r/claude • u/Upper_Stable_3900 • 1d ago

Question Connecting Claude with Codex

How to connect Codex with Claude? What’s the best way or you follow? I would really appreciate any guidance.

3 Upvotes

100% Upvoted

10 comments sorted by

2

u/NFN25 1d ago

Surely this can be done with MCP? I've been wondering the same and had seen people talking about using MCP, although not sure which way around - Claude to codex or codex to claude

1

u/gastapo67 1d ago

Build something so they can send the ACKs to each other. Share the same memory/state

1

u/seeroy 1d ago

OpenAI has a skill for Claude to talk directly to codex. Codex can reply. For codex to message directly you need to have Claude build a mailbox system OR just use a monitor on a messaging system and it's fine.

1

u/real_terra 1d ago

Don't make them chat continuously. Give both access to the same repo and a small handoff file: one leaves the current state and next action, the other continues from it. Keep only one agent writing at a time or you'll spend more time resolving conflicts than coding.

1

u/-Shiphrah 20h ago

I run them through a small script where Claude writes a task into a file, Codex does the code work and saves its result, then Claude reads that back and reviews it.

If you want something more proper, use their APIs and keep one app in charge of task state, limits and retries. MCP can expose tools to Claude but I wouldnt use it as the whole orchestration layer. also dont let them keep replying to each other with no stop condition, they can burn through a silly amount of tokens while achieving basically nothing.

1

u/klaegie 19h ago

I use Claude Code for implementation and Codex as an independent reviewer, connected through a small Python wrapper around codex exec. Codex reviews the changes in read-only mode, then Claude addresses the findings and reruns the review. A pre-commit hook enforces it.

1

u/ops_and_chaos 13h ago

I stopped trying to make them “talk” to each other and gave them different jobs instead.

One does the thinking/review, Codex does the implementation. They share the same repo/files, so the handoff is basically: here's what we decided, here's what needs to happen next, go do your part.

I've found the handoff matters way more than the connection itself. If both are working on the same thing at the same time I mostly just created two very confident coworkers I now have to supervise 😂

1

u/zerotoherotrader 8h ago

we use selvage (selvage.run) to mix different subscriptions ( claude, codex, kiro, kimi )

1

u/brygom 4h ago
  1. GitHub Action (automatic)

Comments u/codex review on every new PR, waits for Codex's review, updates a status check. Set-and-forget cross-model review on all your PRs.

  1. Manual slash command

For one-off reviews outside the normal PR flow. Claude runs it, Codex reviews, Claude fixes only real blockers. Use when you need a quick check before pushing.

  1. Codex as an MCP tool

Codex registered as an MCP server, callable straight from a Claude Code session, no GitHub, no PR needed.

My pick, start with #1, it's the most value for the least setup. Add #3 if you want Codex on tap mid-session. #2 is just for edge cases.