SuperAPI AI Directory
Partner with us中文AI newsFavorites
All toolsAI agentscos-codex-bridge

cos-codex-bridge

Local MCP that lets a Chief of Staff client find, create and register Codex projects; submit exact prompts; track durable receipts; continue existing tasks; and organize scoped work inside all

Open website

About this tool

Purpose

CoS Codex Bridge is a local MCP server that lets the Chief of Staff client discover Codex tasks, create project work, deliver complete prompts, track progress, and continue the same session. It also provides an optional Claude Code CLI route, using local project folders and saved CLI sessions.

Main Capabilities

  • Turn research or product ideas into new Codex projects and tasks.
  • Send complete prompts and additional text without manual copy-pasting.
  • Find existing Codex tasks, read progress, and continue the same session.
  • Track delivery using persistent receipts, rather than assuming accepted prompts have run.
  • Rename, assign, pin, and unpin scoped work in approved projects.
  • Limit local project access through explicit allowlisted directories.
  • Claude Code route (beta): pass provider:"claude-code" to bridge_projects, bridge_sessions, and bridge_submit to start and continue Claude Code CLI work.

How to Use

Installation requirements: Node.js 22+, npm, a locally authenticated Codex CLI and/or Claude Code CLI, and a local client that supports stdio MCP. Codex Desktop registration also requires Codex Desktop on macOS.

Installation steps:

  1. Clone the repository from GitHub or install a pinned version using npm.
    • Stable (Codex only): npm install @0.1.4
    • Beta (Codex + Claude Code CLI): npm install @0.2.0-beta.1
    • Or git clone https://github.com/AV-Labs-Co/cos-codex-bridge
  2. Run the local installer to generate the private configuration, launchers, and MCP snippet at ~/.local/share/cos-codex-bridge.
  3. Paste the generated mcp-client.json into the client's MCP configuration.
  4. Use the bridge_* tools.

Default execution is read-only; use --write only for approved project edits. Choose specific project roots, never the entire home directory. If the CLI is not in the MCP client's PATH, add --codex /absolute/path/to/codex or --claude /absolute/path/to/claude.

Use Cases

  • Turn research ideas into Codex projects and track the build.
  • Send a complete implementation brief to Codex and monitor it, then continue the same task to add review findings.
  • Start Claude Code CLI work in an allowlisted folder and continue the same saved session.

Limitations

  • Requires the user to already have Codex or Claude Code access.
  • The Claude Code route is beta; the locally tested version is Claude Code 2.1.269.
  • Known limitation: if the session already has an active writer, sending a steering prompt will wait for a natural pause/stop point; long autonomous runs may require a human to click Steer.
  • Desktop-owned paused queue recovery is deferred to v0.1; a human may need to click Steer.
  • Sidebar rendering for newer versions of Codex Desktop is unverified; check the compatibility table before use.
  • Receipts are stored locally in plaintext to ensure receipt integrity and should not be considered encrypted storage.
  • Direct worker processes disable inherited connectors and deny permission approvals. Desktop queues use the existing task's permissions and tools; the bridge cannot enforce a narrower sandbox within an already running task.
  • Does not authorize automatic store submission, social posting, or publication.
  • The bridge does not claim "state of the art," full account control, or comprehensive autonomy.

Related tools

Browse category