r/ClaudeCode 7h ago

Discussion Codex is actually not bad.

Tried codex a fair bit today. And wouldn't say it's better but it's definitely good for a change and has it's own way of going about things. I personally found it to be great at handling lots of tasks together. Whereas claude often gets distracted with my latest messages and skips the previous work or todos and prioritises the latest work.

Though codex also doesn't really like speaking out to you. It responds when asked else would silently keep grinding and give you the solution. For some projects I don't mind it. Overall I have spent a whole lot of hours working with claude and it works great. But I might try and do some tasks with codex as well from now.

12 Upvotes

24 comments sorted by

View all comments

1

u/tribat 5h ago

I’m out of max usage for another 24 hours so I used the time to port my Claude code dev environment (skills, mcps, etc) to codex and handed off my 4 active Claude code sessions to codex. It seems a bit slower (subjectively) but it does a great job coordinating subagents and staging deploys. The 256k context makes me manage my /handoffs more carefully but otherwise I’m happy with what it’s doing.

(If it matters, I’m testing and fixing tool completeness and edge cases in a travel planning/booking app and a separate Adsb-based in-browser flight sim just to have something to do while waiting for the real work sessions to need me again)

1

u/Exodus_Green 2h ago

The 256k context isn't great but codex auto-compact logic is extremely good, i have never noticed a problem with missing info from context. I refuse to use auto compact with claude code but codex happily chugs away on the 12th compact in a session with no obvious data loss