When I pair Claude and Codex, I use claude-co-commands [0] to drive from Claude and talk to Codex via MCP. Lately I've found Codex has been far more consistent for my specific projects, so I've just been almost entirely inside Codex. YMMV

[0] https://github.com/SnakeO/claude-co-commands

Yea I'll take the review feedback from one, validate it, and then copy/paste it into the other session saying like, "hey I got this feedback, what do you think?" So I'm not even telling the other AI the feedback is valid, I want it to independently validate it. Often the feedback is not like a bug, but a red flag, design consideration, or trade off.

Often depending on how complex the feedback, I'll do it one at a time addressing each one individually. And after the feedback is addressed, I'll go back to the AI that generated the feedback and say like, "I handled 4/5 items you found, can you double check."

It's similar to handling PR feedback, where you do it, validate it, but then still have to submit it for peer review.

Having the agents write their plans into text files and iterating on those works reasonably well.

Just switch models whenever you want with the menu at the bottom of the chat window in Cursor.

And maybe don't use tools that lock you into one model?