4 ms·

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,

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.

avereveard 3mo ago
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
- bredren 3mo ago
  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. If you're open to giving it a try, I'd appreciate any feedback: https://contextify.sh https://contextify.sh recent show hn: https://news.ycombinator.com/item?id=48777790 https://news.ycombinator.com/item?id=48777790
  - nberkman 3mo ago
    Sounds similar to the tool I built: https://github.com/neilberkman/ccrider#ccrider https://github.com/neilberkman/ccrider#ccrider (although it's OSS whereas yours appears to be commercial)
  - mptest 3mo ago
    > how are yall carrying context... 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
  - avereveard 3mo ago
    steering: You are the sole owner of the project implementation. User maintained documentation: - goals.md for the project overall goals - tech.md for guidance on how to build the project Agent maintained documentation, current state living specs, these are not logs: - project.md is a map of the code, components and features. - choices.md write here all decision taken by the user. Do not duplicate information between these document.
tyteen4a03 3mo ago
Why not both? T3 Code exists.
- reassess_blind 3mo ago
  Hadn't heard about it. Launching either "codex" or "claude" from cli isn't exactly a pain point I was looking to fix. Edit: I guess the real answer is that I don't want multiple subscriptions. I use one for a month, and then decide if I switch to the other.
- xyzsparetimexyz 3mo ago
  Nice try theo
- orliesaurus 3mo ago
  theo's alt account
behnamoh 3mo ago
How? I'm pretty much locked into Claude Code and even if gpt models are good now, the experience with codex CLI has been so bad I won't go back to it. e.g., it still doesn't have /revise or /undo!
- reassess_blind 3mo ago
  I've never used /revise or /undo, everything I do is just through natural language and seems to work great.
- skeptic_ai 3mo ago
  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.
- theshrike79 3mo ago
  Pi.dev makes GPT models a lot smarter, the codex harness isn’t very good
- satvikpendem 3mo ago
  Use the Codex desktop app.
- rane 3mo ago
  Try https://github.com/raine/claude-code-proxy https://github.com/raine/claude-code-proxy I canceled Claude plan a few months back and have been using this. OpenAI plans are much more generous.
ramshanker 3mo ago
Same here. Late to agentic party. 1st month was Codex, 2nd Claude, already thinking 3rd will be Codex again! Since Fable will be gone soon.
bberrry 3mo ago
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.
- mixtureoftakes 3mo ago
  How do you have access?
  - satvikpendem 3mo ago
    OpenAI said in their initial blog post that certain organizations, probably big tech, have early preview access.
- hodgehog11 3mo ago
  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. What type of work is this for in your experience?
atraac 3mo ago
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).
- satvikpendem 3mo ago
  That's an IDE difference not a model difference, it's called steering vs queuing.

avereveard 3mo ago

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

bredren 3mo ago
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. If you're open to giving it a try, I'd appreciate any feedback: https://contextify.sh https://contextify.sh recent show hn: https://news.ycombinator.com/item?id=48777790 https://news.ycombinator.com/item?id=48777790
- nberkman 3mo ago
  Sounds similar to the tool I built: https://github.com/neilberkman/ccrider#ccrider https://github.com/neilberkman/ccrider#ccrider (although it's OSS whereas yours appears to be commercial)
- mptest 3mo ago
  > how are yall carrying context... 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
- avereveard 3mo ago
  steering: You are the sole owner of the project implementation. User maintained documentation: - goals.md for the project overall goals - tech.md for guidance on how to build the project Agent maintained documentation, current state living specs, these are not logs: - project.md is a map of the code, components and features. - choices.md write here all decision taken by the user. Do not duplicate information between these document.

tyteen4a03 3mo ago

Why not both? T3 Code exists.

reassess_blind 3mo ago
Hadn't heard about it. Launching either "codex" or "claude" from cli isn't exactly a pain point I was looking to fix. Edit: I guess the real answer is that I don't want multiple subscriptions. I use one for a month, and then decide if I switch to the other.
xyzsparetimexyz 3mo ago
Nice try theo
orliesaurus 3mo ago
theo's alt account

behnamoh 3mo ago

How? I'm pretty much locked into Claude Code and even if gpt models are good now, the experience with codex CLI has been so bad I won't go back to it. e.g., it still doesn't have /revise or /undo!

reassess_blind 3mo ago
I've never used /revise or /undo, everything I do is just through natural language and seems to work great.
skeptic_ai 3mo ago
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.
theshrike79 3mo ago
Pi.dev makes GPT models a lot smarter, the codex harness isn’t very good
satvikpendem 3mo ago
Use the Codex desktop app.
rane 3mo ago
Try https://github.com/raine/claude-code-proxy https://github.com/raine/claude-code-proxy I canceled Claude plan a few months back and have been using this. OpenAI plans are much more generous.

ramshanker 3mo ago

Same here. Late to agentic party. 1st month was Codex, 2nd Claude, already thinking 3rd will be Codex again! Since Fable will be gone soon.

bberrry 3mo ago

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.

mixtureoftakes 3mo ago
How do you have access?
- satvikpendem 3mo ago
  OpenAI said in their initial blog post that certain organizations, probably big tech, have early preview access.
hodgehog11 3mo ago
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. What type of work is this for in your experience?

atraac 3mo ago

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).

satvikpendem 3mo ago
That's an IDE difference not a model difference, it's called steering vs queuing.