Three Days with Claude Fable 5 — and Why Opus Stays My Daily Driver

Martin Rau · 12. Juni 2026 · 4 Min. Lesezeit

I’ve spent the last three days running Anthropic’s new Claude Fable 5 across multiple editors, throwing real tasks from real projects at it. No benchmarks, no synthetic tests, just everyday development work. Here’s what I found.

The setup

My approach was deliberately unremarkable: the same agentic coding sessions as always, across several editors, with the same effort and deep-thinking settings I use with Opus 4.8. No configuration changes, no special prompting. Just a model swap, and everything else left exactly as it was. That’s the way I wanted it, because that’s the only way you get a fair comparison.

Quality: a different angle, not a different league

Overall quality is solid, maybe a tick above Opus 4.8 — but not because it’s smarter across the board. What really stands out is something else: Fable finds different solution paths.

The best example was a JWT token refresh bug I’d already gotten stuck on twice with Opus. Both times, Opus went in circles — plausible-looking attempts, no real fix. Fable approached the problem from a completely different angle and produced something that actually looks promising. It still needs full testing, so no victory lap yet — but the fresh perspective alone was worth something.

That’s the pattern I’d highlight: when one model gets stuck in a local optimum, a different model isn’t simply “more compute” — it’s a second opinion.

And that’s less obvious than it sounds. Once Opus has settled on a particular reading of a problem, it will try plenty of variations — but all of them within that same underlying interpretation. Fable seems to roll the problem up from scratch, as if it had never seen the earlier dead ends. With this token bug, that was exactly the difference: not “one more attempt,” but a different starting point. For stubborn bugs you’ve already sunk your teeth into, that turns out to be surprisingly valuable.

It talks way less. Way, way less.

Fable is noticeably less chatty. I changed nothing in my settings, so this is clearly coming from the model itself. It looks like the community feedback about models over-explaining everything has landed at Anthropic.

My feelings about it are mixed. After getting used to the detailed running commentary, a model that just… works… silently… feels almost weird. No little summary at the end, barely any status updates along the way. You send it off, and it comes back with results. Efficient? Yes. Comfortable? That takes getting used to.

Speed and token consumption: the real story

Here’s where it gets less fun.

Speed, at identical effort and deep-thinking settings, is noticeably slower than Opus 4.8. And token consumption is massive. On the Max plan I could work all day with Opus without ever touching my limits. With Fable I slipped into the red zone for the first time in weeks. The different token economics are very real.

The token math is real

Fable 5 is priced above the Opus tier. In practice that means a workday that comfortably stayed within budget on Opus pushed my quota into the red with Fable for the first time in weeks. That’s not a footnote — it’s the main reason for my verdict.

My verdict after three days

The marginal quality gain doesn’t justify the massive token consumption — at least not for my daily workload. Opus 4.8 already performs really well on the tasks I throw at it.

Where I do see Fable’s place: as a precision tool for the genuinely hard problems. When you’re stuck, when the complexity genuinely demands the biggest model available, or when you need a fundamentally different perspective on a problem — that’s when I’d reach for it. Deliberately, selectively, as the exception.

For everything else, Opus 4.8 stays my daily driver. Sometimes the biggest model isn’t the best tool — it’s the last-resort tool.

Entdecke mehr

Blog

Themenuebersicht

KI-Modelle Claude