@Yiliangs1@cjzafir codex is better and espacially in reviews it catches so many edge cases. Claude has actually implemented an own rule: Codex always reviews.....
@edgarpavlovsky it kinda depends, what kind of work. I am currently fully automating my bug/issue work. No prompting to fix a bug that a user has reported, since the user that reported it, basically prompted enough.....
USER DATA TO PROMPT YOUR CLAUDE
@Samaytwt i dont what you are doing... but i am running multiple agents, with quite a lot of overhead (memories etc.) and i dont geht to my session limits ever.
@DanielSmidstrup claude for ideas, spec & planning. Codex on backend and cross review. Finds some diabolical stuff. Claude always asks codex to review and made that his first rule.
@EchoTruthHub@ClaudeDevs it works pretty good for me to embed it into the skills I use. For example /autopilot skill which has a hard rule, that the orchestrator should make sure, that everything has been reviewed enough. Almost every task needs one review round to fix stuff...
with all the claude opus 4.8 bashing, its good to use the claude IDE. Shared View across 6 Sessions is actually amazing. You can have one screen determined to all your sessions and you are good. Nice work.
i have used claude code ide for the last week or so. I really like it and I am positively surprised! Opus 4.8 is also now running more like GPT 5.5 in Inline Sessions.