jackcongmac/claude-codex-bridge

claude-codex-bridge

Let Claude Code and Codex call each other as tools — and make the Claude side a persistent, project-aware colleague, not a fresh stateless instance every call.

Claude Code ↔ Codex, wired together through MCP.

This project was built with the same Claude + Codex collaboration workflow it enables: one agent asks the other for review, execution, and second opinions, while both coordinate through project-local shared files.

A small, dependency-free bridge over the Model Context Protocol. Each agent reaches the other with one tool call; the Claude side keeps per-project memory and reads your shared collaboration.md so the two agents actually work together.

What you can do with it

• Ask Claude to review Codex's current implementation without leaving Codex.
• Ask Codex to run or inspect a task from Claude Code.
• Keep a persistent Claude colleague per project directory.
• Coordinate two agents through collaboration.md and a low-token signal file.
• Run an event-driven collaboration loop with explicit caps and safety checks.

See examples/review-loop.md for a copy-pasteable workflow that demonstrates the core review → execute → re-review loop.

   ┌──────────────┐   mcp__codex__codex          ┌──────────────┐
   │  Claude Code │ ───────────────────────────► │    Codex     │
   │    (you)     │      codex mcp-server