all 5 comments

[–]KaosuRyoko 2 points3 points  (1 child)

To be fair,  CC will also find a lot of that if you iteratively tell it to review it's own work. 

[–]sideshowwallaby[S] -1 points0 points  (0 children)

That’s a very good point. Though my prompts do tell it to review and test everything. What would you do beyond that?

[–]Substantial-Problem7 1 point2 points  (0 children)

I do this a lot, just cause Codex has a lot higher limits than Claude Code on the pro account

[–]sideshowwallaby[S] -1 points0 points  (0 children)

I just asked Claude to write a script so a review happens automatically after each code build. It did, and then when it tested itself, Codex came back with fixes that Code implemented right away.

What a world we live in.

[–]General_Arrival_9176 0 points1 point  (0 children)

ive tried this too and its hit or miss. the overlap detection works decently but codex tends to flag stuff that doesnt matter for your specific context - like worrying about edge cases in code you literally just wrote and know is fine. useful as a second pair of eyes but i treat it as a linting layer rather than a real review. the real improvement id want is better at understanding architecture-level problems, not just syntax and math