Codex Control Plane MCP

What Codex Control Plane MCP does

A client submits a task or starts a Plan Mode workflow and gets an operationId or workflowId back immediately. It then polls status, answers approvals or approves the plan, and reads a final report. The server takes on app-server startup, thread and turn creation, retry safety, duplicate prompt protection, approvals, local history, diagnostics and repair. Reusing the same client_request_id on a retry returns the existing operation instead of starting another turn.

Other capabilities include attaching image inputs to new turns, steering an active turn, forking a thread, archiving and unarchiving threads, starting thread compaction, and requesting a structured final report through an output_schema. Status payloads return only safe metadata about images, and the README says the server does not extract hidden chain-of-thought or store raw tool payloads in final reports. Because Plan Mode needs a writable workspace on Windows, a read-only default is raised to workspace-write and the adjustment is reported in status.

Key features

• Immediate operationId or workflowId with polling for status
• Retry safety through client_request_id and duplicate prompt protection
• Plan Mode workflow with plan approval before execution
• Steer, fork, archive and compact Codex threads
• Structured final reports through output_schema
• Diagnostics, local history and repair tools

When to use it

• Letting an orchestrator hand Codex Desktop a multi-hour task without holding one MCP call open
• Approving a Codex plan from another agent before it executes
• Retrying a timed-out request without creating a duplicate turn

Who it is for: Developers who run a local orchestrator or agent, such as Hermes or OpenClaw, and want Codex Desktop to handle long jobs reliably.

How it fits with Hermes Agent

The README calls OpenClaw and Hermes first-class clients, though the server suits any local orchestrator that speaks MCP.

Requirements: Codex Desktop with codex-app-server, and an MCP client.

FAQ