pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for Codex Control Plane MCP

Pod holds 16 of 18 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to Codex Control Plane MCP.

Most discussed

Add redacted account, usage, and rate limit status

Goal

Expose a privacy-safe account and quota status view from Codex app-server.

Candidate app-server methods

  • account/read
  • account/usage/read
  • account/rateLimits/read

Privacy rules

  • Do not return tokens.
  • Do not return raw email by default.
  • Do not return account identifiers unless explicitly needed.
  • Prefer booleans and coarse status fields.

Acceptance criteria

  • Health/runtime capabilities can show whether Codex is authenticated.
  • Rate-limit information is inc

Read the thread · 2026-06-17 · closed · 2 comments

Sync Codex thread goals with workflow state

Goal

Use Codex app-server thread/goal/get, thread/goal/set, and thread/goal/clear to synchronize high-level workflow goals.

Why

The MCP workflow already has durable goal-like state. Mirroring it into Codex thread goals can improve visibility in Codex Desktop and make resumed threads easier to understand.

Acceptance criteria

  • Workflow start can optionally set a thread goal.
  • Workflow completion can clear or update the goal based on configuration.
  • `codex_get_workflow_status

Read the thread · 2026-06-17 · closed · 2 comments

Add thread lifecycle management tools

Goal

Expose safe thread lifecycle operations around Codex app-server thread management.

Candidate operations

  • thread/archive
  • thread/unarchive
  • thread/compact/start
  • possibly thread/delete only behind explicit destructive confirmation

Design notes

These should stay outside the hot write path. They are management/maintenance tools, not replacements for durable operations.

Acceptance criteria

  • Archive and unarchive are available as safe MCP tools.
  • Compact is avail

Read the thread · 2026-06-17 · closed · 2 comments

Support outputSchema for structured final reports

Goal

Allow MCP clients to pass Codex app-server outputSchema through durable task and workflow operations.

Why

OpenClaw/Hermes can use structured final reports directly:

  • summary;
  • root cause;
  • proposed fix;
  • risks;
  • touched files;
  • analyst comment draft;
  • developer plan.

Proposed shape

  • Add optional output_schema to codex_submit_task.
  • Add optional output_schema to workflow planning/execution where appropriate.
  • Persist parsed final JSON in final_report_json w

Read the thread · 2026-06-17 · closed · 2 comments

Add durable thread fork operation

Goal

Expose Codex app-server thread/fork as a durable operation.

Why

Forking lets an MCP client safely branch from an existing thread:

  • try an alternative analysis;
  • continue from an older state;
  • compare two solution plans;
  • keep the original thread intact.

Proposed shape

  • Add operation type fork_thread.
  • Accept source threadId, optional target cwd/config overrides, and optional initial message.
  • Persist new threadId as soon as app-server returns it.
  • If an initia

Read the thread · 2026-06-17 · closed · 2 comments

Add runtime capabilities endpoint for Codex app-server inventory

Goal

Add a read-only runtime capabilities endpoint that summarizes what the local Codex app-server can do.

Data to include

  • app-server platform and user agent from initialize;
  • supported schema methods from generated or cached schema;
  • available models from model/list;
  • permission profiles from permissionProfile/list;
  • sandbox readiness from windowsSandbox/readiness;
  • hooks status from hooks/list;
  • skills count from skills/list;
  • model provider capabilities from `mod

Read the thread · 2026-06-17 · closed · 2 comments

Capture richer app-server progress events in the journal

Goal

Persist a richer, redacted progress journal from Codex app-server notifications.

Events to support

  • item/agentMessage/delta
  • item/plan/delta
  • item/reasoning/summaryPartAdded
  • item/reasoning/summaryTextDelta
  • turn/diff/updated
  • thread/tokenUsage/updated
  • model/rerouted
  • warning
  • configWarning
  • guardianWarning

Constraints

  • Do not store raw command output by default.
  • Do not expose raw tool payloads by default.
  • Keep sensitive text redacted or tru

Read the thread · 2026-06-17 · closed · 2 comments

Support image and local image inputs for Codex turns

Goal

Allow MCP clients to send image inputs supported by Codex app-server turn/start.

Use cases

  • attach screenshots for UI/debug analysis;
  • pass error dialogs or visual evidence;
  • include local image files in a task.

Design notes

  • Validate file paths and size limits.
  • Do not copy image contents into logs.
  • Store only metadata in operation diagnostics by default.
  • Keep the text-only API path unchanged.

Acceptance criteria

  • codex_submit_task accepts image/local image

Read the thread · 2026-06-17 · closed · 1 comment

Most recent

Add durable code review workflow via review/start

Goal

Expose Codex app-server review/start as a durable MCP workflow for code review scenarios.

Proposed behavior

  • Start a review through app-server.
  • Persist review operation and associated thread/turn ids.
  • Poll progress through existing operation/workflow status.
  • Capture final review output as a structured report when possible.

Open questions

  • What input shape should be public: branch, diff, PR URL, local checkout, or all of them?
  • Should this be a separate tool or an op

Read the thread · 2026-06-17 · closed · 1 comment

Add durable turn steering without creating duplicate turns

Goal

Expose Codex app-server turn/steer through the durable operation layer so an MCP client can add context to an active turn without starting a second turn.

Why

OpenClaw/Hermes often needs to pass a clarification while Codex is still working:

  • add an analyst note;
  • ask for an additional technical plan;
  • answer a question from the user;
  • correct scope without creating a duplicate turn.

Today the safe path is mostly "start another turn later". turn/steer should make this a fir

Read the thread · 2026-06-17 · closed · 1 comment

Publish troubleshooting guide from real install failures

Turn real install and setup failures into a troubleshooting guide. Include symptoms, likely cause, and the exact command or config change that fixes each case.

Read the thread · 2026-06-17 · open · 0 comments

Improve first-run security presets

Review the first-run security posture and propose safer presets or clearer prompts for users who start with untrusted repositories.

Read the thread · 2026-06-17 · open · 0 comments

Add comparison docs for thin Codex wrappers

Expand the README comparison into a short docs page that explains when a thin wrapper is enough and when a durable control plane is useful.

Read the thread · 2026-06-17 · closed · 1 comment

Collect MCP client config examples

Collect working MCP client config snippets for common clients. Keep secrets out of examples and prefer copy-paste snippets that work with the PyPI package.

Read the thread · 2026-06-17 · open · 0 comments

Add Docker/devcontainer smoke environment

Add a lightweight Docker or devcontainer setup for protocol smoke checks. This should help contributors run tests without needing a full local Codex Desktop setup.

Read the thread · 2026-06-17 · open · 0 comments

Test live workflows on macOS

Run the live workflow checks on macOS and document what works, what is protocol-only, and what needs platform-specific handling before macOS can be claimed as a full live target.

Read the thread · 2026-06-17 · open · 0 comments

The remaining reports are on the project's issue tracker.