umum-ai/claude-codex-bridge

umum-ai/claude-codex-bridge

Claude Codex Bridge

Run OpenAI Codex agents from Claude Code. Ask Claude to delegate a task to Codex, follow its progress, send another instruction while it works, stop it, or continue a saved session.

The plugin connects Claude's MCP tools and Channels to codex app-server. Codex tasks run asynchronously; starting a task returns its session ID without waiting for the task to finish.

sequenceDiagram
    actor You
    participant Claude as Claude Code
    participant Bridge as Bridge plugin
    participant Codex as Codex app-server
    You->>Claude: Delegate a task to Codex
    Claude->>Bridge: codex_start
    Bridge->>Codex: Start a thread and turn
    Bridge-->>Claude: Session ID
    Codex-->>Bridge: Progress, questions, result
    Bridge-->>Claude: Channel notifications
    You->>Claude: Add an instruction or stop
    Claude->>Bridge: codex_message / codex_stop
    Bridge->>Codex: Steer / interrupt the turn

Requirements

• Claude Code 2.1.261, installed and signed in.
• Codex CLI 0.153.4, installed and signed in with access to the model you want to use.
• Node.js 24.20.0 or newer, including npm and npx.

These are the tested versions. Older versions are unsupported; compatibility with newer versions must be verified. The plugin uses the experimental Codex app-server protocol and Claude Code Channels research preview.

node, npx, and codex must be on the PATH inherited by Claude Code. The npm package includes the bridge's JavaScript dependencies. The plugin uses npx to fetch its exact package version on first startup; subsequent starts use npm's cache. No source build or protocol generation is required.

Install

1. Check the required tools

Install Claude Code, Codex CLI, and Node.js, then check:

claude --version
codex --version
node --version
npm --version
codex login status

If Codex is not signed in, run codex login. Claude and Codex use their own accounts and model access. The plugin does not provide a subscription or API credits.

2. Add the marketplace and install the plugin

claude plugin marketplace add umum-ai/claude-codex-bridge
claude plugin install claude-codex-bridge@claude-codex-bridge --scope user

Claude installs the plugin from this repository's marketplace. The plugin starts the pinned version of @kvokka/claude-codex-bridge with npx --yes. The first startup needs access to the npm registry.

3. Enable the plugin and Channels

Merge this into ~/.claude/settings.json, keeping your other settings:

{
  "channelsEnabled": true,
  "extraKnownMarketplaces": {
    "claude-codex-bridge": {
      "source": {
        "source": "github",
        "repo": "umum-ai/claude-codex-bridge"
      }
    }
  },
  "enabledPlugins": {
    "claude-codex-bridge@claude-codex-bridge": true
  }
}

The installation commands already register the marketplace and enable the plugin. The complete fragment above also shows how to reproduce the settings.

4. Start Claude in your project

cd /absolute/path/to/your/project
claude

The maintainer reports that channelsEnabled: true enables this ordinary startup on Claude Code 2.1.261 without a shell alias or wrapper. Channel activation can also depend on your account and organization policy. Verify incoming progress with the example below before relying on it.

Anthropic's Channels documentation currently describes channelsEnabled as a managed setting and requires per-session opt-in. If tools load but incoming progress does not arrive, see Channels troubleshooting.

Use it

Talk to Claude normally. Give Codex a concrete task, the project directory, and an explicit model when you want one:

Use the bridge to start Codex with model gpt-5.6-luna in /absolute/path/to/my-project. Review the authentication code and suggest a fix for the failing login test. Report its progress as channel events arrive.

To check that notifications work, use a task with a short delay:

Start Codex in this project. Ask it to announce that it started, run a command that waits 15 seconds, and then reply BRIDGE_DONE. Wait for channel events; do not poll codex_status or codex_events.

While Codex is working:

Tell that Codex session to focus on the token refresh path.

To interrupt it:

Ask that Codex session to stop.

After a task completes:

Continue that Codex session: implement the proposed fix and run the relevant tests.

Keep the threadId if you want to continue after restarting Claude:

Resume Codex thread THREAD_ID in /absolute/path/to/my-project, then ask it to continue the investigation.

Claude can list available models with codex_models. An explicitly selected model is requested without provider fallback.

Available tools

Tool	What you can ask Claude to do
codex_models	List the models available to Codex.
codex_start	Start an independent task in an absolute project directory.
codex_message	Send an instruction during a turn, or start the next turn.
codex_stop	Interrupt the current turn.
codex_resume	Reopen a saved Codex thread.
codex_answer	Answer a structured question from Codex.
codex_status	Read status, pending questions, and the latest answer.
codex_events	Read recent events using a sequence cursor.

How it works

Claude starts the plugin as an MCP server. The plugin starts a local codex app-server process and uses its stdio protocol to manage Codex sessions. Control calls return promptly; the task continues inside Codex. This does not use a long-running Claude Bash tool call, and task duration is independent of Claude's Bash timeout. Control acknowledgements have a 30-second timeout.

Codex progress, questions, errors, and completion arrive through Claude Channels. Claude processes queued notifications when it can take its next turn. A successful notification write does not confirm that Claude has read it. Codex sessions appear through tools and messages, not as native Claude agents in its subagent panel.

Codex runs with danger-full-access and approvalPolicy: never. It can modify files and run commands with the permissions of your local user without requesting approval. Claude's tool permissions do not sandbox Codex. Choose the project directory and tasks with that execution mode in mind.

The plugin uses Codex's existing authentication and configuration. It adds no API proxy, model impersonation, interception hook, or global timeout override. Exiting Claude stops the bridge and its app-server process. Saved Codex threads can be resumed; running work is not hosted by a background daemon.

Progress is batched about once a second and capped at 8,000 characters per batch. The bridge retains 200 recent events across sessions and up to 64,000 characters of the latest answer. Truncation and an expired event cursor are reported explicitly. The event journal lives only for the current bridge process.

Update or uninstall

To install the latest published version:

claude plugin marketplace update claude-codex-bridge
claude plugin update claude-codex-bridge@claude-codex-bridge

Restart Claude after updating. To remove the plugin:

claude plugin uninstall claude-codex-bridge@claude-codex-bridge --scope user
claude plugin marketplace remove claude-codex-bridge

Why yet another connector?

codex-mcp explains why existing solutions on the market fall short, and why a straightforward approach was needed.

I checked all the boxes, but the implementation ended up large and clumsy.

This version is ~14× smaller (10 321 LOC in codex-mcp v3.1.0 vs 746 LOC in claude-codex-bridge v0.1.2), more stable, clearer, and cleaner. It builds on Claude Code Channels — still experimental, but solid enough in practice.

It has the same limitations and the same feature set as codex-mcp.

I only arrived at this design after shipping codex-mcp. The idea isn’t new: it was already implemented in codex-claude-bridge. That project is unmaintained, and this architecture fixes several of its flaws.

Releases

A release is chosen manually with exactly one release:patch, release:minor, or release:major label on a pull request. It runs when the PR merges into main, or when the label is added to an already merged PR. An unlabeled PR publishes nothing.

The release updates the npm package version, both root versions in package-lock.json, the plugin manifest, the marketplace entry, and the npm version in the plugin's launch command together. It checks the resulting commit before pushing main and the X.Y.Z git tag atomically, then publishes the verified npm archive with provenance and creates the GitHub release. If main moves during the checks, the release stops before tagging.

For a failed publication, run the release workflow manually with its existing X.Y.Z tag as ref. This retries that version without another bump. An npm version already carrying the same archive is left in place; different bytes are rejected.

The npm package owner must configure a trusted publisher for GitHub owner umum-ai, repository claude-codex-bridge, workflow release.yml, and environment npm. The first publication uses the repository's short-lived NPM_TOKEN secret. After the package exists and its trusted publisher is configured, npm uses GitHub OIDC; the token can expire or be removed. The token is passed only to the publication step.

Troubleshooting

Tools work but live progress does not arrive

Tool availability and incoming channel delivery have separate gates. Use codex_status to confirm the task is running and check Claude's startup notices for a channel or organization-policy warning.

For testing this custom channel, start a session with:

claude --dangerously-load-development-channels plugin:claude-codex-bridge@claude-codex-bridge

This explicit preview flag is the integration-tested path for incoming events. The plugin is not on Anthropic's official channel allowlist. An organization can approve it in managed settings with channelsEnabled: true and an allowedChannelPlugins entry naming marketplace claude-codex-bridge and plugin claude-codex-bridge; an approved session uses --channels plugin:claude-codex-bridge@claude-codex-bridge. Preserve any other channels on the organization's allowlist.

The MCP server fails to start

Check that node --version, npm --version, and codex --version work in the same terminal where you launch Claude. Restart Claude after installing either tool or changing PATH. Use /mcp in Claude to inspect the server connection.

Codex rejects the model or account

Run codex login status and ask Claude to call codex_models. Model access is controlled by your Codex account. A requested model error is surfaced directly.

A task disappeared after restarting Claude

Ask Claude to call codex_resume with the saved threadId and project directory. The event journal does not survive a restart; the saved Codex conversation does.

Report reproducible problems at GitHub Issues, including the tool versions, the failed operation, and relevant error messages. Remove credentials and private project content from reports.