I’m bouncing back between Codex and Claude like a ping-pong ball. I much prefer the experience using Codex, less verbose and to-the-point I’ve found. But Fable, being as strong as it is, is a big draw for Claude right now. I’ll likely switch back to Codex if 5.6 Sol is comparable.
I personally like Codex much more as vscode integration. It's actually nice to use, looks great, handles images much, much better, can even send me images in the chat to see what it's doing(my side project is based heavily on image processing), and what's most important to me is that /steer actually works. When I type something to Claude mid-task, it'll maybe acknowledge that within next few minutes, although it seems to be actually quicker last few days but still takes a minute or two, whereas Codex will almost instantly read it, switch what it's doing or answer me. It feels much more polished in some ways(though usage page in settings almost never loads for me).
Same. For some reason late opus model are very superficial doing ux work and so am using gpt for that, but backend is much better engineered by claude, gpt prefer to duplicate everything it needs on the spot causing class sprawl
How are y'all carrying context history from one agent to the other?
I also flip between the models due to quota, TUI enhancements, model updates and service availability.
To handle this, I built a thing that normalizes your transcripts between Claude Code and Codex into a shared DB, then a CLI and skill.
It has made it so it doesn't matter what I built where (or when) I just refer to the work and drop in a /total-recall (or $total-recall on codex) and the agent brings it into the current convo.
I realize there are a lot of ~memory tools out there, but I think particular my approach and product behavior is unique.
Personally I just , in the orchestration loop, have all decisions be constantly reviewed and deliberated on and the decisions logged in a permanent way, that way everything is auditable, the model if needed can go back and look at why x or why decision was made or x or y tool used, and they're all labeled as D-1234 or whatever.
Plus I have it log the council discussions and always include provenance or the opinions so fable can go back after every major implementation and review how the orchestration loop could be improved. Basically have it log as much thinking in an organized compartmentalized way is better than any memory feature I've found though I haven't tried many. Auditable logs for every major decision, use 5.5 with reckless abandon (still have 3 resets myself).
Not claiming this is perfect but it has led to a very easy time of any fresh agent picking up the project. I also keep a task queue and project status and agent playbook that also get refined based off the logs of how a run went
How can be locked? If you have a proper agents in your project it will work out of the box with any model. I use codex and Hermes on same project with 0 issues. Skills, MCP and other features are useless imo.
My agent has access to glab with a user and can do whatever within permissions. No need a MCP. MCP maybe just for browser control.
5.6 Sol is extremely good, definitely Fable level from my experience. With 5.6 Sol being half the price and noticeably faster I think Anthropic will find the coming months unpleasant.
I would be absolutely stunned if this were really the case in general given how irresponsibly large Fable is, and 5.6 Sol most definitely is not. It depends on what your problems are though, I suppose, since there are those that swear Fable is at best a minor upgrade over Opus, which has not been my experience.
