Hey y’all, Wanted to share a workflow setup I’ve been running that turned out better than expected. I gave Codex controlled SSH access into the local machine where my Claude Code setup and testing harness live, then had it audit and optimize the environment around Claude instead of replacing it. To keep the agents from colliding, I have them coordinating through a local MCP/Agent Hub layer that acts like a control room: shared state, message passing, logs, routing, and lightweight context packaging so each agent doesn’t have to reload the whole project every time. The division of labor ended up working pretty naturally:
- Claude Code handles fast local execution, creative iteration, and hands-on feature work.
- Codex acts as a remote auditor/operator over SSH, cleaning up the environment, tightening prompts/hooks, and reducing drift. The interesting part is that it feels less like using two chatbots and more like running distributed workers with roles, rooms, logs, and routing. Claude moves quickly and explores; Codex is good at making the harness stricter, checking assumptions, and cutting down unnecessary ceremony. Not magic, and definitely not free, but if you can stomach the setup cost and subscriptions, the combo is surprisingly effective. I’m still testing this, so I’m keeping the exact prompts/hooks/router details private for now, but the high-level architecture has been very worth it. submitted by /u/WittleSus
Originally posted by u/WittleSus on r/ClaudeCode
You must log in or # to comment.