Testing Claude’s New Fable 5 on a Real Infrastructure Problem

When Anthropic released Claude Fable 5 in June, its first Mythos-class model made generally available, I had a task sitting on the shelf that felt like a fair test: a phone-to-AI-agent SIP bridge I had started, stalled, and restarted with earlier model generations more than once over the past few months. It never quite got over the line. This time it did, in one session.

A rocky launch, then wide release

Fable 5 launched on June 9 as Anthropic’s first broadly available Mythos-tier model, the same underlying model as the more restricted Claude Mythos 5, but wrapped in the strongest safety classifiers Anthropic has shipped to date. Access was suspended just days later, on June 12, after US export controls were applied to both models. The controls were lifted at the end of the month, and Fable 5 returned to general availability on July 1, this time with an improved cybersecurity classifier. For subscribers, it has been available at no extra cost through a trial window that closes today, July 19.

What sets it apart

On paper, Fable 5 is built for long-horizon, autonomous work: holding an entire problem in view across many steps rather than needing constant back-and-forth. Reviewers who put it through real coding and infrastructure tasks during launch week reported the same pattern, fewer rounds of correction, more of the work done correctly on the first pass, particularly on long, open-ended jobs rather than quick questions. That description matched my own experience closely.

Finishing what I’d started

The task was a SIP trunk and call-in setup: routing an incoming phone call through Asterisk into a LiveKit voice agent. Conceptually straightforward, practically fiddly, and it had defeated a few earlier attempts. I gave Fable 5 the requirements, the existing stack, and the constraints, and it came back with a complete architecture, the full set of configuration files, and a detailed step-by-step setup guide, all in a single pass. I followed the plan on the server and the first end-to-end test call went through cleanly: ringing, answer, two-way audio with the agent, clean hangup. What normally would have taken a few more frustrating sessions took one afternoon.

A glimpse of what’s coming

The catch is cost. Now that the trial period has ended, using Fable 5 means paying per API token rather than drawing on a subscription, and at roughly double Opus-tier pricing, it isn’t a model to reach for by default. On bacher-ai.com, API access to Fable 5 is available on request only, since the usage cost is too high to offer freely. Still, the trial gave a useful preview: this is roughly where AI-assisted infrastructure work is headed as Mythos-class capability gradually becomes standard rather than exceptional. I would rather see that curve now than wait for it to arrive.

Key Takeaways

  • Claude Fable 5 is Anthropic’s first Mythos-class model made generally available, launched June 9 and briefly suspended over export controls before returning July 1.
  • It’s designed for long-horizon, autonomous work, and independent reviews consistently note fewer correction rounds on complex, multi-step tasks.
  • It completed a SIP trunk and call-in architecture, config, and setup guide that had stalled across several earlier model generations, and the resulting deployment worked on the first real test call.
  • The free trial period ends July 19; going forward, usage is billed per API token at a premium over Opus-tier pricing.
  • API access to Fable 5 is available on bacher-ai.com by request only, given the cost of offering it freely.
Scroll to Top