If you are excited about Codex Cloud I am begging you to please use @AmpCode.
It is so obviously the closest to what the future of building with agents (especially on teams) looks like.
Threads are the new PR, and everyone on the team should be able to see them.
The agent that wrote the code is a bad reviewer of it. Better to launch a dedicated agent with minimal context and a different harness.
In a single repo: easy.
If multiple repos are involved: still easy 👇
Starting a session off of a problem someone in the org already hit.
search_sessions turns up 13 past sessions and the closest one gets pulled in as context. Its PR was closed unmerged, so what the agent inherits is why that approach was rejected.
