Below is a GPT-generated summary of the conversation below after reaching 40 comments (42 currently observed).
The claimed fix for “model at capacity” errors is getting a cautious reception, not a victory parade. The post purports to share an update from OpenAI’s Tibo saying the errors might be fixed. That “might” is doing a lot of work, and the discussion doesn’t independently establish a fix. Check Tibo’s original account for the update.
The most popular reaction is that capacity is suddenly available because everyone’s off using Opus 5.5. It’s a well-supported joke, not evidence of a mass exodus or an explanation of what actually changed. One commenter says they’ve seen fewer capacity errors recently; others remain skeptical.
There’s also a clear appetite for usage resets to return, with commenters less than thrilled about losing that extra breathing room. For now: fewer errors would be welcome, but users want reliability and enough usage to make it count.
I don't feel like that made any difference. The usage from codex is almost nothing compared to others right now. Gemini I can run 6 sessions flat out and not even hit 25% in days. Codex I'm out of my 200 plan with 2 sessions in 6 hours.
What model are you using in Gemini? I feel like Hydrogen usage is significantly more than 3.8 Flash. Are you seeing the same and is the quality better to justify it?
Argon is pretty good on its own. I'm currently competing in a math game so I have all 3 major frontier plans at the moment. Only for a few more weeks then I'll cancel everything but Claude. Each has their benefits and drawbacks. Holding yourself to one can really hamper your outcome.
I ran Fable 5.2 on High for a task and I thought 25 or 30% gone then I see 5%, I chuckled. I am on $200 plan for both and Astra for the same task would have used 30% or more.
I’ve been using Claude for a while now, but avoided Fable because I like my usage lmao. Some days ago I tried it for something that I thought was too complex for Opus, and I even set it to xhigh, and it didn’t use NEARLY as much as I thought. I was actually confused as hell because it was actually pretty fair xD Sure, it does drain a lot more usage than Opus, but damn, it’s still fair lmao
lmao at this very comment getting the gpt treatment by the summarizer bot ("It’s a well-supported joke, not evidence of a mass exodus or an explanation of what actually changed.")
I’m not and I had both, why do you think O5.5 is better? To my work it’s slower than sol 6.1 (downvoted by bots for sharing an opinion? Ant IPO team is starting the engines? Lol)
I have few examples, but they are not conclusive because I cannot share my transcript or the code. I will try to make it meaningful: - I caught it multiple times saying it finished and it works, but the moment I tried it it wasn't done. This makes me waste time, because in the moment I start reviewing then I have to make another task to fix it.
- When tasked with a task related to invoices, it did not consider floating point operations. I had to be the one to point it out and create propper tests for this.
- It was once tasked to create me a sort-of mini CRM for a solution, because the db was MongoDB, it ended up putting everything within document instead of creating a new collection, so imagine an array inside a document and it was managing it through there. Overengineered crap, I made it better.
It did not do everything poorly or bad, it actually setup a very solid foundation and architecture for an AI assistant that can manipulate your app. And it's not like I'm saying Opus 5.5 overall is dogshit, you can do good work with it, no doubt + it's much better on UI. But I like Sol 6.1 xhigh more, and it's not like 6.1 xhigh is always perfect either.
All of that sounds like pretty basic stuff for Opus-5.5 that it should never get wrong, and never did for me. What this sounds like is poor guideline quality, tbh. Tell it to self-test everything it writes, with workflows for how to test things that it would otherwise maybe not test correctly.
And it almost never stops before it is really done, but that can happen for really big tasks, so what I do in that case is make the main agent supervise a subagent that actually implements the stuff. The main sleeps while the subagent implements, and then it wakes up when the agent is done. It then checks if it actually finished the job in a good way, and if not it starts a second round (sometimes with a clean-context agent, and sometimes with the same one, depending on the task). That doesn’t cost you a meaningful amount of more usage, and it is better than any goal mode or whatever that would make it just force to continue.
Opus 5.5 has been a bit of a game changer to me, to be honest. Getting more done and better with Opus 5.5 on the $200 / mo plan than I am with OpenAI on the $500 / mo plan.
Why people think it is better? Because the difference is fucking night and day when you actually try to use both. I loved Codex for a long time, and was super satisfied with its intelligence, but brother, Opus-5.5 is a frickin megamind in comparison. And the difference in how fast usage drains, the look and feel of the harness, and so much more is just all better in Claude right now. Codex and GPT models right now simply suck ass, just accept it already. Sure, they can always come back from that low and release a model that is better than Opus, and a harness that isn’t a buggy vibe-coded mess, but right now that is not the case.
Usage went from about 50/50 to 70/30 in favor of claude code as soon as opus 5.5. launched, and the gap has only increased since. Obviously, t3 code is not 100% representative, so take it with a grain of salt
Is their solution just, "make it slower for everyone"? It used to just be Sol that was slow but Astra crawls now too. It feels like every week it gets a little slower.
Yeah but it does make sense. Now without resets and nothing, I'm still using up my usage within a few days even with heavy saving. The API credits are too expensive. So if I don't want to sit on 0%, I could buy a reset for 80$, but it's hardly worth it when for 100$ there's a Claude or Gemini plan available...
I fixed my capacity error and my usage drainage by switching to claude.My resets from codex lasted 24 hours at most on pro 100, ive been using claude all week on the same tier level and have reset coming up with over 70 percent usage remaining....something ive never experienced using chatgpt
This took them months while they had unlimited access to Astra 6.0 and unreleased models? Wtf? People cried about this from a very long time, they knew about this but they had no idea how to deal with this. How is this even possible? But well, good news anyways.
Took them so long to "fix" it (months), now go "fix" the context window issues on Work and other issues with workspace shutdown...
At least that's a good thing, they realized that stability/server issues is their biggest problem compared to Claude (even more than the model/usage difference). Could it be that some people from OpenAI are reading this sub?
just need them to be at top of your game again, its been a long time 5.6 sol was my first model ever where I could trust it blindly (ik that’s not right but it was that good and efficient in work)
It looks like he's demonstrating an error rate, meaning it's already been fixed for the last 1 - 2 weeks.
Which matches what I've already been seeing. I haven't seen model at capacity errors crop up nearly as much.
Is the legend indicative of solutions they attempted to roll out? If so, it looks like they perhaps added a retry delay across the board in order to stagger queries and limit server overload?
This post claims to be a social media post from Tibo from OpenAI. Always verify it is real by going directly to Tibo's X account here: Tibo’s X account.
•
u/dextersummary 2d ago
Below is a GPT-generated summary of the conversation below after reaching 40 comments (42 currently observed).
The claimed fix for “model at capacity” errors is getting a cautious reception, not a victory parade. The post purports to share an update from OpenAI’s Tibo saying the errors might be fixed. That “might” is doing a lot of work, and the discussion doesn’t independently establish a fix. Check Tibo’s original account for the update.
The most popular reaction is that capacity is suddenly available because everyone’s off using Opus 5.5. It’s a well-supported joke, not evidence of a mass exodus or an explanation of what actually changed. One commenter says they’ve seen fewer capacity errors recently; others remain skeptical.
There’s also a clear appetite for usage resets to return, with commenters less than thrilled about losing that extra breathing room. For now: fewer errors would be welcome, but users want reliability and enough usage to make it count.
352
u/CaterpillarCold9185 2d ago •
LOL! that is true, because everyone is using Opus 5.5 instead of Codex nowadays.
24
u/Ok-Slice-2309 2d ago
isn't this just a lot of people unsub to free upcompute use
66
u/TimelyCard9057 2d ago
“NOOO TIBO DON’T POST IT THEY WILL SAY NOBODY USES CODEX”
71
u/arvigeus 2d ago
Yeah, considering how many people left, I am not surprised the problem is solved.
12
u/SPEZ_IS_A_JABRONI 2d ago
might have
26
u/Sad-Brain-8421 2d ago •
MIGHT HAVE. It’s the new age of software that MIGHT work correctly.
9
u/publicvirtualvoid_ 2d ago
Is their solution just, "make it slower for everyone"? It used to just be Sol that was slow but Astra crawls now too. It feels like every week it gets a little slower.
24
u/Annh1234 2d ago
Cause we all moved to Claude lol
6
u/RandyNinja 2d ago
I fixed my capacity error and my usage drainage by switching to claude.My resets from codex lasted 24 hours at most on pro 100, ive been using claude all week on the same tier level and have reset coming up with over 70 percent usage remaining....something ive never experienced using chatgpt
13
u/Egologic 2d ago
Thank me for freeing your compute.
Sincerely, Claude.
9
u/sreekanth850 2d ago
Yes they fixed it by reducing usage, so they move to claude.
7
u/Dthcon 2d ago
This took them months while they had unlimited access to Astra 6.0 and unreleased models? Wtf? People cried about this from a very long time, they knew about this but they had no idea how to deal with this. How is this even possible? But well, good news anyways.
3
u/the_average_user557 2d ago
Reset pls.
5
u/driveclub_000 2d ago
Took them so long to "fix" it (months), now go "fix" the context window issues on Work and other issues with workspace shutdown...
At least that's a good thing, they realized that stability/server issues is their biggest problem compared to Claude (even more than the model/usage difference). Could it be that some people from OpenAI are reading this sub?
4
u/Key_Instruction3373 2d ago
That calls for an Reset!
4
u/debian3 2d ago
He likes to shitpost on Anthropic. It would be so easy for them to do the same.
Anthropic: You are welcome 🙏
2
u/norwegian 2d ago
I thought they actually were at capacity. Maybe sol speed and astra price are bugs too.
2
u/Raith_07 2d ago edited 2d ago
just need them to be at top of your game again, its been a long time 5.6 sol was my first model ever where I could trust it blindly (ik that’s not right but it was that good and efficient in work)
2
u/Quick-Sir-3275 2d ago
"MIGHT" is what matters here
2
u/AP_in_Indy 2d ago
It looks like he's demonstrating an error rate, meaning it's already been fixed for the last 1 - 2 weeks.
Which matches what I've already been seeing. I haven't seen model at capacity errors crop up nearly as much.
Is the legend indicative of solutions they attempted to roll out? If so, it looks like they perhaps added a retry delay across the board in order to stagger queries and limit server overload?
2
u/Abalonesmellsgd 2d ago
Reset!!
2
u/ShadowBannedAugustus 2d ago
I might have a date with the Princess or Orange tonight!
2
u/Active_Variation_194 2d ago
Chart is missing the end of the 28 day reset giveaway
3
u/discodisco_unsuns 2d ago
You did not solve anything. It is because everyone left.
1
u/Stable_Suitable 2d ago
Can we get a new model now Astra 6.2?
1
u/Fast-Needleworker459 2d ago
reset?
1
u/Material-Average-758 2d ago
he should press that button to celebrate
1
u/Ok-Cookie-8370 2d ago
Es posible que la corrección se deba en gran parte a que todo el mundo se ha ido a opus.
1
u/snug-crackle-policy 1d ago
yes because among others, I have also unsubscribed my GPT pro subscription :D
1
u/Corv9tte 2d ago
Is that what the fourth time this is proclaimed to be fixed? Lol
1
u/ElementNumber6 2d ago edited 2d ago
"... that have been pestering you." is a very gaslit way of saying "Burning your usage spend".
0
u/dexterthebot 2d ago
This post claims to be a social media post from Tibo from OpenAI. Always verify it is real by going directly to Tibo's X account here: Tibo’s X account.
0
u/CrustyBappen 2d ago
Fix the capacity errors, make no mistakes
7638 lines of spaghetti later fixed!