I use Claude for planning, writing CRs, and code review.
Codex writes all of the code, no exceptions.
Works great, especially when you ask Claude to break up large CRs into roughly 10 minutes of Codex work each.
I use Claude for planning, writing CRs, and code review.
Codex writes all of the code, no exceptions.
Works great, especially when you ask Claude to break up large CRs into roughly 10 minutes of Codex work each.
Same here. I find the design, architecture, system design discussion to be better on Claude, but after Opus 4.6 I switched over to Codex for actual coding and love the results. I use both via the CLI and generally tell Claude to output the result of our decisions as a markdown that will be easy to read and implement by an agentic coding tool. Then I fire up Codex and read said markdown as the input of the session and way to build all the appropriate context needed. I see this as a way to step into letting the agents go run on their own and interact with each other, but I still like to steer so I put these manual steps in the flow. Letting the agents go off on their own and one shot big chunks is not reliable enough yet imo.
I do exactly the opposite.
I think the key is to get two LLMs looking at the same problem.
I use Codex because it's better at the kind of code I need written (math-heavy, 3D geometry code).
But if I was doing mainly UI code, I would do the opposite.