Claude Codex Collab

Claude × Codex Collab

**Two AI coding agents. One orchestrator. Zero API costs.**

A dead-simple system that makes Claude Code and OpenAI Codex CLI work together as a team — Claude as the PM, Codex as a second engineer. They debate architecture, delegate implementation, and cross-review code. All running on your existing subscriptions. No API keys. No third-party tools. No MCP servers. No tmux. Just bash, markdown, and slash commands.

You → Claude Code (PM + orchestrator)
       ├── Claude subagents (deep codebase work)
       └── codex exec via bash (independent implementation + fresh perspective)

Why this exists

Every developer using AI coding agents hits the same ceiling: **one model, one perspective, one set of blind spots.** Claude is great at architecture and nuanced reasoning. Codex is great at fast, focused implementation. But they don't talk to each other.

Until now, your options were:

• Copy-paste between terminals (tedious, breaks flow)
• Third-party orchestration tools (complex setup, another dependency)
• MCP bridges and messaging bots (overengineered for the problem)
• Just pick one and ignore the other

This system takes a different approach: **Claude Code calls Codex directly via bash.** That's the whole trick. `codex exec` runs headlessly and returns output to stdout. Claude reads it as a regular tool result. No infrastructure. No coordination layer. The filesystem and bash are the only "middleware."

What it actually does

Think — Two models debate your problem

You ask a question. Claude forms a position, then calls Codex to challenge it. They go back and forth for up to 2 rounds. Claude synthesizes both perspectives and presents a recommendation.

/collab Should we use event-driven architecture or cron-based scheduling for our background jobs?

Claude doesn't just relay Codex's response — it **reasons about it**, identifies where they agree, where they diverge, and who has the stronger argument. You get a synthesi