And Just Like That, Fable 5 Was Gone — Vanished at 3 AM

3 AM, and Suddenly Nothing Worked

July 18, 2026, 3 AM. I was about to keep working with Fable 5 like any other night. I'd already set my model to Fable 5 with /model and saved it as my default, so all I had to do was throw a prompt at it.

The moment I sent the prompt, this showed up:

› /model
  └ Set model to Fable 5 and saved as your default for new sessions

› back to work

● Usage credits are required for this model.

* Crunched for 0s
                          ~267k uncached · /clear to start fresh

Crunched for 0s. Zero seconds. It bounced before it even started. The model was clearly set to Fable 5, but the moment I tried to run it, all I got was one line — "Usage credits are required for this model." — and nothing happened.

At first I assumed I'd burned through my session limit. I'd been at it into the small hours, so it wasn't a wild guess.

I Opened the Usage Panel — and Fable 5 Was Missing

So I opened Settings → Usage. The result wasn't what I expected.

Item	Status
Plan	Pro
Current session	47% used (resets in 4h 19m)
Weekly limit (all models)	44% used (resets Fri 12:59 AM)

My session wasn't even half full, and the weekly limit sat at just 44%. This had nothing to do with hitting a limit.

The truly strange part was elsewhere. Fable 5 itself was gone from the usage list. A model that was there just the day before had been quietly dropped from the list overnight. All that remained was the combined "all models" gauge — no trace of Fable 5 as something I could use on its own.

To sum up the situation:

1. Fable 5 was still selectable as a model, and even saved as my default.
2. But the moment I ran it, it stopped in 0 seconds saying "credits are required."
3. In the usage panel, the Fable 5 entry had vanished entirely.

In other words, the days of just using Fable 5 on the Pro plan had quietly come to an end. From now on, using this model would require separate usage credits.

When You See "Usage credits are required"

In case someone else runs into this message at 3 AM and panics like I did, here's the order I'd check things in.

1. First, figure out whether it's a usage-limit problem

If you'd genuinely maxed out your limit, the message would be different. A limit overrun usually comes with something like "your session resets in X." But Usage credits are required for this model. is a billing/credits problem, not a limit problem. If your session and weekly gauges have room to spare under Settings → Usage and you still see this, it's not a limit — the model's access policy changed.

2. Check whether the model is still in the usage list

If a model like Fable 5 has dropped off the list entirely, that's a sign it's no longer included by default on your plan. A name lingering in the model picker and the model actually being runnable on your plan are two different things.

3. If you still need it, you have two options

• Add credits or move up to a higher plan (to keep using a model that requires usage credits).
• Switch to a different model included in your plan (change it with /model).

I just switched my urgent work to a model included in my plan via /model and wrapped up. I really didn't feel like pulling out my card at 3 AM.

Wrap-Up

• Out of nowhere at night, Usage credits are required for this model. popped up and my Fable 5 work stopped in 0 seconds.
• It turned out this wasn't a session or weekly limit issue — Fable 5 had been dropped from the usage list entirely on the Pro plan.
• Even though the name still showed in the model picker, actually running it now required a credits-only model.
• If you need to keep working right away, switching to a plan-included model with /model is the fastest workaround.

It always stings when a model you liked quietly disappears from your plan — especially one you'd saved as your default and used happily. But changes like this come around now and then. Just reading the message carefully — is it a limit, or credits? — can save you from wandering around confused at 3 in the morning.