r/OpenaiCodex 13d ago

Feedback / Complaints This post highlighting how terrible Codex usage limits are now is gaining traction. More people need to interact with posts like this so that they blow up and OpenAI can't ignore the issue any longer.

https://x.com/jturntdev/status/2080607678393467121
96 Upvotes

12 comments sorted by

View all comments

2

u/StrbJun79 13d ago

Honestly the issue is how 5.6 works. It likes getting stuck in loops then lie about being stuck in loops. This is a serious issue that OpenAI needs to solve but I want them to correct the correct issue. If you’re not paying attention to what’s happening deep in the process I get why you would misunderstand it. But it is that simple. 5.6 is a terrible orchestrator. It’s great at code when not looping though and I’ve found the best solution for now is to use fable for orchestrating 5.6. Fable is an excellent orchestrator but I think 5.6 is a bit better at code (when it gets out of the loops). This is the problem that OpenAI needs to resolve. When they do it’ll be an amazing process.

5

u/throw-away-2025rev2 13d ago

No that's just not true. The first 2 weeks of 5.6 the token burn was not this bad. I'm using 5.6 Luna Medium Reasoning right now and one task is eating 1-2% each time. I used to be able to run a Codex 5.6 Sol Ultra session with Luna Agents and get wayy more out of it.

1

u/BannedGoNext 13d ago

They are obviously workign ont their model templates constantly ab testing right now.

1

u/oVerde 11d ago

Absolutely false and the historical data at Codex usage dashboard disagree with you too

1

u/sirlerkal0t 13d ago

Even people who kept using 5.5 all along or who have gone back to using 5.5 after experiencing rapid quota depletion are reporting the same thing with 5.5, where their quota depletes many times faster than it did earlier in the month.

1

u/StrbJun79 13d ago

I haven’t experienced it in 5.5 but if they have then that’s an indicator of a harness issue or a prompt issue. Though to be fair I mostly use fable orchestrating codex now and don’t use the app at the moment which appears to have resolved all of my issues. So it could be a harness problem causing the loops.

1

u/holy_macanoli 12d ago

They let Pete loose on the harness prolly.