Codex Claude Bridge
An open-source multi-AI collaboration bridge tool that uses a local MCP server to let OpenAI Codex act as a planner orchestrating Claude Code to execute specific coding tasks. It supports Git worktree isolation, session management, and result review, enabling programmatic orchestration between two AI programming assistants.
Timeline (last 90 days)
Codex Claude Bridge is an open-source project that lets OpenAI's Codex act as an orchestrator, delegating coding tasks to Claude Code for execution and reviewing changes, with the entire workflow connected through a local MCP bridge layer.
Developers only need to give Codex three things: a goal, a workspace, and acceptance criteria, with the remaining coordination handled automatically by the bridge layer.
Codex Claude Bridge supports session management, allowing the creation of new Claude Code sessions or reconnection to existing sessions via UUID to ensure context continuity.
Codex Claude Bridge uses isolated delegation, assigning tasks in separate Git worktrees and reviewing and merging afterward, so that experimental changes do not contaminate the main branch.
Codex Claude Bridge allows independent adjustment of interaction frequency and reasoning effort, and can reuse previous inspection results when the source snapshot, environment, and scope match.
Codex Claude Bridge preserves existing Claude Code model configurations, including third-party providers.
Codex Claude Bridge supports both Windows and macOS platforms; Orca is optional and a regular terminal works fine.
Running Codex Claude Bridge requires Codex CLI, a working Claude Code configuration, Node.js 20+, and Git.
Codex Claude Bridge is installed via Codex's plugin marketplace using two commands: codex plugin marketplace add and codex plugin add.
The author of Codex Claude Bridge is seeking feedback on three aspects: session recovery, task handoff, and coordination overhead.
1 more timeline events
All Facts (11)
Codex Claude Bridge is an open-source project that lets OpenAI's Codex act as an orchestrator, delegating coding tasks to Claude Code for execution and reviewing changes, with the entire workflow connected through a local MCP bridge layer.
50%UnverifiedDevelopers only need to give Codex three things: a goal, a workspace, and acceptance criteria, with the remaining coordination handled automatically by the bridge layer.
50%UnverifiedCodex Claude Bridge supports session management, allowing the creation of new Claude Code sessions or reconnection to existing sessions via UUID to ensure context continuity.
50%UnverifiedCodex Claude Bridge uses isolated delegation, assigning tasks in separate Git worktrees and reviewing and merging afterward, so that experimental changes do not contaminate the main branch.
50%UnverifiedCodex Claude Bridge allows independent adjustment of interaction frequency and reasoning effort, and can reuse previous inspection results when the source snapshot, environment, and scope match.
50%UnverifiedCodex Claude Bridge preserves existing Claude Code model configurations, including third-party providers.
50%UnverifiedCodex Claude Bridge supports both Windows and macOS platforms; Orca is optional and a regular terminal works fine.
50%UnverifiedRunning Codex Claude Bridge requires Codex CLI, a working Claude Code configuration, Node.js 20+, and Git.
50%UnverifiedCodex Claude Bridge is installed via Codex's plugin marketplace using two commands: codex plugin marketplace add and codex plugin add.
50%UnverifiedThe author of Codex Claude Bridge is seeking feedback on three aspects: session recovery, task handoff, and coordination overhead.
50%UnverifiedOrchestration overhead introduces additional latency and token consumption with each round-trip between Codex and Claude Code, and when tasks are broken down too granularly, the coordination cost may exceed the cost of direct execution.
50%