My experience with Fable 5

My own experience with Fable 5 has been very positive, especially for coding and planning.

I spent around 500m tokens on it over the past few days across real engineering work: architecture, debugging, code review, and implementation planning.

The biggest difference from Opus 4.8 is discipline. Fable 5 is less talkative. No huge explanations, no 100-line comments above every method, no re-explaining basic software concepts back to me. When I ask for a fix, I get the fix, not a refactor of half the module.

It also does not overengineer. It reasons about the actual task, stays inside the scope I gave it, and stops when it is done. For real engineering work, that matters a lot.

Where it really earns its keep is judgment. It steps back, sees the bigger design problem, and pushes back instead of blindly following the prompt.

Sometimes the best AI response is not "yes, I will implement this," but "this design may be wrong, and here is the risk."

That is where I see Fable 5 fitting into my workflow: planning, architecture, difficult debugging, and code review.

I still would not route every small ticket through it. Per token, it is expensive. But for serious engineering problems, the value is not only in the code it writes. It is in the better decisions it helps you make.

One thing developers should keep in mind: Fable 5 looks like Anthropic's first API-first usage-priced model. It is available in Claude Code now, but this access seems temporary. In the next few weeks, it is expected to be excluded from the normal subscription plan and move to usage-based credits.

But overall: less noise, better judgment, stronger reasoning.