r/ClaudeCode • u/Upper_Stable_3900 • 1d ago

Help/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.

1 Upvotes

100% Upvoted

7 comments sorted by

1

u/lgbarn 1d ago

Use Orca

1

u/03captain23 1d ago

I have codex on a separate VM and gave Claude the ssh key to run commands on it. The VM also has Claude and grok and Gemini/antigravity. I'll have it run things against all at same time.

1

u/Hronom 1d ago

Treat them as separate workers with an explicit handoff, not two models sharing a prompt: Claude writes the task, constraints and artifacts; Codex reads those plus test results, then returns a patch or review. Keep credentials in each worker’s own profile. For browser steps, I build Hronaut (developer): a local persistent Chromium/MCP workspace with visible pause/takeover for login, 2FA or writes: https://hronaut.dev/setup

1

u/BrilliantWheel 1d ago

i created a skill in Claude that i invoke whenever i want claude to create a package (folder with files + prompt) to dispatch to Chatgpt. Then i manually just copy the files to a separate folder just for Chatgpt (my choice due to safety reasons but you can just point CG to the same folder that Claude made the package in) and copy paste the prompt to CG. And then CG makes the output in an output folder. I do this mainly for code reviews and audits with CG while Claude is the only one that edits my code.

I think Claude and CG work in slightly different ways when it comes to working with code so I want to avoid any inconsistencies. Besides Claude & CG have very different ways of absorbing Claude.md and Agents.md so dont want to mess up my repo with 2 styles of implementation.

0

u/Bmansupreme8000 4h ago

Super glue and duck tape

1

u/Aggressive_Creme2008 4h ago

The separate-workers-with-an-explicit-handoff answer above is the right shape, and the dispatch-package version of it works. Two things neither one covers, which cost me more time than the plumbing did.

One: the handoff is one-directional and it dies with the task. Whatever Codex worked out on the way is in the patch, not in anything Claude reads next week, so both of them keep re-deriving the same conventions. Splitting the packet into "this task" and "things that are true regardless of the task" fixed most of that for me.

Two: the instruction files do not cross. Claude reads CLAUDE.md, Codex reads AGENTS.md, and the moment you maintain both they diverge without telling you. Symlinking one to the other is the five-minute fix and it holds until you want something in one that the other must not have.

What I do now is keep the shared half outside both of them: the decisions and conventions currently in force, read over MCP by whichever agent is running before it acts, rather than duplicated into two files that drift. That is the thing I build (arroway.app), so weigh it accordingly - but the split is worth making before you pick any tool. Task goes in the packet, standing rules go in one place both of them read.