I did find a strategy, thank you very much, and it was easy:
reply npm uninstall -g @openai/codex && curl -fsSL https://claude.ai/install.sh | bash
OpenAI devs, if you're reading, this is how you lost a customer.
Claude does the same?
replyIt asks you to create new chats (Claude Design) and Claude Code nudges you to start over too, I think `/compact` is optional though?
Claude does the same when you hit the context limit, but the difference is that claude's context limit is 1m and Codex's is 272k now. Claude lets you get a lot more done before you have to worry about the start getting compacted away.
replyHave you observed any decrease in performance at context higher than 200k?
replyThat used to be one of the major issues why clearing or compacting context when the context nears 150 to 170k is usually preferred.
Opus: Yeah, it can be a little fuzzy at 600-700k, I prefer it 400K and under in general. But, I've had usable sessions to 850k.
replyIt really depends on the session, and what you are doing how far you can push it.
Not really, on the project I'm working on right now most of my longer prompts seems to consume somewhere between 300k and 400k tokens (input + output) and I find that both Opus 4.8 and Fable 5 don't seem to get lost with that much context. At least the results still look good to me.
replyI don't think I've ever pushed past 500k though, it may well fall apart at the higher end of what is officially supported.
I see it more past 300-350k these days, but probably there is a smaller decline even past 250k.
replyThere are numerous Claude settings to disable or modify this behavior
replyCodex context limit is 400k total, including 128,000 reserved output tokens.
replySo you went from a bad product to a worse product? There’s good solutions out there and you’re like “nope don’t want a good solution. I want a worse solution.”
reply^ this is literally what the op did. Don’t flag facts.
[dead]
reply[flagged]
replyThis would have been a great opportunity to suggest one.
reply[flagged]
reply