KiS Blog

Claude Fable 5: Where It Runs, What It Costs, What Got Removed

July 22, 2026 · From the video recorded July 1 · 9 minutes

Update since the video: Anthropic has since made Fable 5 a permanent model rather than a limited promotion. The July 7 cutoff below was the original promo window. The rest still applies: where it runs, the usage mechanics, and what was stripped out.
The short version
  • Paid plans only. Pro, Max, Team, Premier and Enterprise got Fable 5 at no extra cost during the promo; free plans were excluded. It launched with a cap of 50% of your weekly usage.
  • It burns usage faster than Opus 4.8, and it gets its own meter in the app so you can watch exactly what it is drawing down.
  • Two things were taken away: coding was stripped out of the model, and auto mode would not run with it. Opus stays the coder; Fable directs.
  • It still earned its keep in one test: it fixed three interface problems in a 3D visualization that two other models had left broken.

Where it shows up

Fable 5 is not one product in one place. It appears across web, mobile, desktop, Cowork, Claude Code, Claude Design, the Microsoft 365 integrations, Claude for Teams, and the Slack Claude tag. In Claude Code on the command line you can see it directly: type "models" and Fable 5 is right there next to Sonic 5.

Two version gotchas from setting it up. Claude Code needs version 2.1.170 or newer, so update if you do not see the model. And the desktop app had to be relaunched after its own update before Fable 5 appeared there; once it did, the app defaulted to Fable 5 on its own, labeling it the most capable model.

What they took away

The headline is not what Fable 5 does, it is what it no longer does. Coding was stripped from the model, so it will not help you write code. The practical shape of that: Opus 4.8 remains the coder, and Fable 5 sits above it more like a delegator deciding what should happen.

The second removal hurt more in practice: auto mode. With Opus you can hand Claude Code a job, switch on auto mode, and let it run to the finish without babysitting. With Fable 5 selected, auto mode reported it was not available for the model, and the session fell back to approving edits by hand. If your workflow is built on walking away while the work runs, that is a real cost.

The test: could it fix what other models left broken?

The test bed was a 3D visualization of my second brain, a graph you can spin, zoom, and click into. It had three long-standing annoyances: rotation wobbled off its axis, the topic filters never actually filtered, and the zoom was so quirky it was hardly usable. Earlier passes with Opus 4.8 and another model had found errors but left the behavior broken.

Fable 5 fixed all three. The graph now spins on its own axis, unchecking a topic actually hides it, and the zoom throttling works. Same project, same request, different model, working result.

The honest verdict from the video: knowing what was stripped out, it felt like "Fable 4.5." But if the model in front of you makes the thing you are building better, use it and keep it moving. The label matters less than the output.

Why this matters if you run a business

Model launches come with dates, caps and asterisks, and they change month to month; this one changed within three weeks of the video. The durable move is not chasing each release, it is having your own material organized so that whichever model is current can pick it up and be useful immediately. That is the case for an AI second brain: the models rotate, your business records compound.

Not sure where AI would save you time?

The free quiz takes 2 minutes and gives you a starting list for your business. No call, no card.

Take the free 2-minute quiz