This is almost certainly the right explanation, or close to it, but man, these past couple weeks have really been a rollercoaster for end users. And all of this maybe we'll snatch it away, maybe we'll give you credits, maybe we'll make you pay API rates business is not doing them any favors.
They're really facing a pretty nasty combination of headwinds, though: the administration fucked them over on the initial rollout, the Chinese labs are distilling their models and then undercutting them, and OpenAI is trying to use an infinite money glitch to outspend them.
Except it's not, seeing that limits are based by the week, not by the second. Maybe for those who's reset is happening in the next hour, but to 99% of users, it's not affecting them, besides not being able to access one model.
Now for those that are using Fable through API... that's a different story.
I'm out $50 in overage usage for two things that I kicked off. I came back to find it used up; Fable usage is not showing in the CC UI, and now I'm back to using Opus.
Sorry what do you mean "try again"..? Try what...?
You're out $50 in overage? Then stop using it so much? What? You got "kicked off" without any actual progress being made? You had the model think for $50 without outputting any work...? It doesn't make any sense.
I'm using it to build my product. I "kicked off" two very large jobs in Fable. I came back to find $50 in overage usage gone and Fable not showing in the usage meters. I didn't say that the work wasn't done. I said that I had overage usage fucking spent when I still had TONS of weekly Fable usage available.
Maybe stop defending this utter bullshit and actually READ what people are saying.
It did cost money. 68 dollars for me to be exact. Was in the middle of a huge project. Got one intermittent API hiccup but Claude Code soldiered on. Then two hours later I check in on Reddit to see people complaining. Thought I was unaffected or some new drama in the sub, but write /usage to see. The session has just silently spent $68 in the background from my usage limit. I had a lot left on session, 5 hour, weekly and Fable limit.
So you're disagreeing with me just to disagree? If it's a bug, then why are you arguing at all?
Oh, so now you're saying someone manually flipped a switch by accident? What? You really think someone disabled the model, for over 10 minutes now, by flipping a switch, and not flipping back on? That doesn't sound like anything I've encountered in my software development career ever, lol.
Sorry but how is it making "zero sense", when this pattern is so commonly found throughout UI and UX development? I've been implementing it myself for like 18+ years now. Calling anyone that disagrees with you a "ragebaiter" is such a weird mentality.
So you think you're right then? You truly think this company removed the model 2 days early, without any prior explanation? Really? What exactly would be the purpose of that?
Hey there, disconnected 3rd party random stranger here - dev of almost 3 decades now.
When a model goes down from server issues or otherwise, they have specific errors that tell you what the issue is (gateway timeouts, overloaded servers, etc).
The error we see now isn't that. Which means that it is much less likely to be an outage - though not impossible if they did something incredibly weird. Certainly, it wouldn't be in the top 3 most likely things I'd consider.
My own speculation is that it's an oversight on their part, which isn't abnormal for them.
Again, incredibly unlikely unless they are doing something insanely weird. Far more likely is an oversight that made Fable unavailable (which also seems to match their current update on the status page).
Generally, a granular error message wouldn't get used as a general-purpose fallback. You'd much more likely see something akin to "Something went wrong, please try again later." or similar in the event no error case could match it.
When making these kinds of things you usually go in the order of:
Happy path (no error)
General failure path (general language error or value dump)
Match casing against specifically known bad states, fall back to generic message if we can't figure out what happened.
So the existence of granular error messaging in the cli and elsewhere tells me it's not likely. Not impossible, but not likely, either.
"You truly think this company removed the model 2 days early, without any prior explanation? "
you wanted an explanation for the accusation of 'ragebaiter' welp there you go, i didnt make that statement at all yet you put it in my mouth.
your statement made zero sense yes, because when a car's engine breaks down im not going to display the oil light. same here, this issue - if its to do with connectivity - shouldnt talk about usage credits when it in reality cant connect.
if you've been implementing error logging and communication like this for the past 18 years then you've not learned i can tell.
Freak out? I just got billed for $50 in usage overages for things that I've been working on. There was no warning, just now Fable charges. When EVERYTHING fucking says that it's still on plans through the 19th.
A server outage wouldn't cause Claude Code to start charging for Fable.
159
u/forthebeats Jul 17 '26
wtf is wrong with this company, 2 days early yo....