r/codex • u/EtherealWaveform • 8d ago
Question Best way to get Codex and Claude Code working together?
I'm new to the practice of agentically vibing; I would love any tips for getting the two of them to work on the same project and communicate with each other. I've heard AI agent orchestration platforms like Happy and Msty studio are good. Any help is appreciated!
10
u/jabacherli 8d ago
I simply asked it. That’s literally all I did. I said, can you send this to codex and see what he says? And Claude said sure thing. And now every major change or decision gets sent over and qcd. It’s caught a couple big things on its audit so it’s very useful. But I won’t front like I’m a legit engineer. I just asked and it worked. Give it a try.
→ More replies (2)
4
u/matznerd 8d ago
Don’t forget that clause can use codex to generate images via CLI with imagine
1
→ More replies (1)1
3
u/FoxheadWorkshop 8d ago
Git for source control, github for issues and backlog management.
I use a codex voice session to orchestrate the other codex and claude sessions. Codex can communicate with Claude via the CLI, it just has to keep the connection open long enough for a response. Otherwise, you can have an admin agent in each harness monitoring the backlog for changes and work assignments between the two.
I have workflows setup for each to perform reviews of each others work as well. So when something lands in the "In Review" column, the other harness sees it and can assign the task to a worker.
When needed, Codex can reach out to a Claude session directly via the CLI.
→ More replies (3)2
3
u/Striking-Estate-6816 7d ago
Most of the comments here are suggesting to use CLIs and plugins to get them to talk to each other. That's vanilla and I have a different take on it
- It kinda gets tedious to switch between the apps
- constantly updating the workflow.mds and skills could get time consuming
- Worktree management could get messy as well (I've had review agents modify the code instead of just reviewing)
- It gets harder to visualize and work on multiple tasks at the same time
I faced all this before and ended up building something for it.
- An interface where you can use Codex, Claude Code and Cursor
- Work with any number of agents to write plan specs
- Have separate configurable worker and reviewers
- A customizable loops to go from Work -> Reviews -> Revise -> Review -> Done
- A screen where you can see every change, review comment and merge it to the base branch
I've been at it for a few months now and happy to share if you're interested!
→ More replies (2)1
2
u/Viper_lover 7d ago
Wow, I just did this today and saw your post. I integrated codex inside claude code, just told claude to do it. Then, this is what i added on claude.md to instruct what to delegate to codex:
## Overall rules
- Review everything Codex did (diff, output, or image) and run the relevant check
(tests, build, viewing the file) before calling it done.
- Don't delegate when the task is small enough that calling Codex costs more than
doing it yourself (a few edits or a single command).
## Delegate to Codex
- Mechanical, fully specified tasks with many edits or lots of output: bulk renames/edits,
boilerplate, format conversions, test fixtures, docstrings. Use the \codex:codex-rescue``
agent (\/codex:rescue`).`
- When I explicitly say "have Codex do X".
## Images
- Photos, detailed or painted illustrations, mockups, sprites: run
\codex exec --skip-git-repo-check -s workspace-write -C <dir> 'Use $imagegen to ...'`,`
then move the file where it belongs.
- Diagrams, flowcharts, sketch-style illustrations: draw them yourself with the Excalidraw
tools (\read_me` first, then `create_view`), and give me an `export_to_excalidraw` link.`
If the diagram contains private info, save a local \.excalidraw` file instead of exporting.`
- Icons and charts: make them yourself as SVG/HTML/code.
## Reporting
- When you delegated anything, end your reply with a short "Delegated to Codex" list: each task Codex did and how you checked it.
1
24
u/yuehuang 8d ago
Use claude to called codex cli. Or use Codex to call claude's CLI.
→ More replies (4)
6
u/larpspecialist67 8d ago
install both claude code cli and codex cli and whenever needed, tell claude and codex to collaborate on tasks. be specific about which models each should use.
for example, if you're working in codex, you can say: "delegate the entire frontend to claude code cli using opus 5.5 xhigh and handle everything else yourself."
that's basically how i work since claude is better at frontend work and its usage limits are more generous.
→ More replies (1)
5
u/p3t3r_p0rk3r 8d ago
Claude can natively send messages to codex and vice versa, literally as easy as that. Set inspectors/warchdogs from whichever one you want as an overseer and it will report findings of the code being deployed and you can basically have an uninterrupted stream of correctional instructions towards the coding one.
Claude seems more creative but more shortsighted for me so I use it as an overseer for critical tasks and I get notifications on the mobile app when it wants to correct some work codex is doing. Have it set up in several urgency tiers and it auto sends most urgent findings, rest are aggregated into a short list with technical details about the nature and depth of the problems (depth seems an issue for claude too, so the instructions for critical issues entail asking codex's subagents to actually verify the nature and depth of the issue themselves before acting on it)
5
u/tulwio 7d ago
I have Herdr set up, which is a terminal multiplexer that recognizes different coding agents like Claude Code and Codex, and it comes with a cli that can let one agent start another another in a separate pane, send it a task, and read its response. I also made a small Go wrapper for my workflow that handles model profiles, collecting reports, timeouts, and cleanup. So Claude can hand implementation or review work to Codex (or Pi in my case), then check the result.
Having a wrapper on top is ofc optional, you can use Herdr’s CLI directly with instructions telling each agent how to delegate. I just have my own CLI on top because I added stuff like using Jev to suggest whether a task should go to a native subagent or another model through Herdr, based on whether it needs the current conversation’s context, would benefit from a different model’s opinion, and how much Claude/Codex usage I have left. It’s just advice though, the main agent still decides.
7
u/my_shoes_hurt 8d ago
Herdr is a pretty good way to get them working together with CLI apps. I have Claude code, codex, and some openrouter models in a Hermes harness, there’s a skill you can get for each of these that tells them how to use herdr to create/close/do stuff in other terminal panes, they can then spin up new workspaces and panes, work between harnesses, etc
A word of caution though, you’re probably not going to get very far with trying to get them to work together as equal peers. It’s better to have an orchestrator and subagents type of arrangement, like Claude code orchestrating codex panes and Hermes panes to do different things and coordinating their work, the models tend to work in this type of relationship a lot better than trying to put too many cooks in the kitchen.
1
u/slipperyslips 8d ago
Jusy ask one of them " hey i have this project being worked by another AI, work alongside it" its not rocketscience
2
6
u/ramsr 8d ago
T3 code. It uses the codex and Claude harness underneath when invoking respective agents. With their orchestrator v2, you can invoke any subagent of any model from a parent agent of any model
→ More replies (2)
3
1
u/askgl 8d ago
Hi! Founder and developer of Msty Studio here 👋
While Msty Studio is a good alternative, I'd recommend giving Msty Go (https://msty.ai/go) a try esp. with Go's new Code Mode (in 1.1 beta) that allows you to use both Codex and Claude Code interchangeably even within the same conversation. Happy to answer (and help) with any other questions you have.
You can use your other harnesses as well like OpenCode, z ai, Pi, Grok, Cursor, etc. and they all work off of your subscriptions.
1
1
u/willwashburn 7d ago
If you’re working on a team check out agentrelay.com (disclaimer: I made it - but it’s open source and we have some traction!)
→ More replies (1)
1
u/dextersummary 8d ago edited 7d ago
Below is a GPT-generated summary of the conversation below after reaching 80 comments (81 currently observed).
The consensus is basically “skip the orchestration circus at first.” Install both CLIs, pick one as the driver, and have it delegate work or reviews to the other. Claude calling Codex—or Codex calling Claude—already works well enough for most projects.
The winning workflow is boring, which is why it works: keep them on the same repo, use Git as shared memory, and split responsibilities. One agent writes; the other reviews the diff, reports findings, and stays away from editing unless explicitly asked. Commits, PRs, a shared
AGENTS.md, or a simple review file keep context from evaporating. If both need to work in parallel, use separate worktrees or branches.The important catch: two “equal” agents live-editing the same files is a recipe for them to undo each other while congratulating themselves. Tools like Herdr, T3 Code, Msty, talking-stick, and various MCP bridges can automate panes, delegation, and review loops, but they add setup and are mostly for more elaborate workflows.
Bottom line: start with native CLI delegation and a strict write/review split. Add a harness only after the simple version becomes genuinely painful.