For in the road

Anthropic just released a coding model that beats Opus 5.5 on two major benchmarks and can complete certain difficult tasks for half the cost.

Yet in its Fable 5.2 announcement on Monday, the company recommended that most developers stick with Opus, calling it the “strongest daily driver” for coding and knowledge work.

“Based on capabilities and pricing, Claude Opus 5.5 is still our recommended model for most everyday work, from coding to knowledge work,” Anthropic tells The New Stack.

“Based on capabilities and pricing, Claude Opus 5.5 is still our recommended model for most everyday work, from coding to knowledge work.”

Anthropic says Fable is intended for large software migrations, multi-agent builds and long-running research, but its performance data complicates the recommendation. The more expensive model can cost less to complete certain tasks, and the company’s proposed multi-model architecture adds considerations around delegation, context management, and execution costs.

When pricier runs cheaper

On FrontierCode 2.0, Fable 5.2 at High effort scored 45.3%, nearly matching Opus 5.5’s best result of 45.5%, while completing the benchmark tasks at roughly half the cost, according to Anthropic.

Fable costs twice as much per token, at $8 per million input tokens and $40 per million output tokens compared with Opus at $4 and $20, yet its reported task cost was lower, demonstrating that token pricing alone doesn’t determine which model is more economical.

Anthropic also cited an internal experiment in which 1,000 Fable 5.2 agents formalized Fermat’s Last Theorem in 30 hours. With the same agent configuration, Opus 5.5 completed only 26% after 18 hours and made little additional progress by the 30-hour mark, according to the company’s published results.

The experiment demonstrates the scale of work Anthropic is targeting with Fable, although it doesn’t establish how much of that advantage carries over to smaller deployments or conventional coding workloads.

Model manager mode

The company is also positioning Fable as a coordinator for less expensive models, so developers can reserve reasoning capabilities for work that other models cannot reliably complete.

“Fable 5.2 can act as an orchestrator that delegates simpler tasks to Opus 5.5 or Sonnet 5.5, or as an advisor those models consult on harder problems.”

“Developers also no longer have to choose just one model,” Anthropic tells The New Stack, “Fable 5.2 can act as an orchestrator that delegates simpler tasks to Opus 5.5 or Sonnet 5.5, or as an advisor those models consult on harder problems.”

For a large software migration, Fable could analyze dependencies, plan changes across services, and delegate individual implementation tasks to Opus or Sonnet. More difficult decisions could then be escalated back to Fable without requiring the more expensive model to perform every step.

Coinbase has already built a multi-model infrastructure that routes tasks based on requirements and cost, and the company says it cut internal AI spending by nearly half even as token usage increased.

Anthropic wants Fable to handle some of those routing decisions itself, although any savings will depend on how often cheaper models can finish the work they’re assigned without needing help, since additional model calls, context transfers and failed attempts can drive up costs over the course of a long-running agent task.

The context-switching tax

There’s another complication when developers switch between models during a conversation. Fable 5.2 can read thinking blocks generated by Opus 5.5, but Opus cannot read those generated by Fable.

This could mean finding another way to pass along relevant context when building systems that move work between models, something that can require additional tokens, not to mention eat into the savings from using cheaper models.

Switch sooner, save more

Anthropic recommends starting with Opus and moving to Fable when higher-effort Opus evaluations fail to meet a project’s requirements, providing a capability-based switching rule that doesn’t necessarily account for the lowest total execution cost.

Its FrontierCode results show Fable achieving comparable performance at roughly half the task cost, so it is probable developers could benefit from switching earlier than Anthropic recommends.

Its FrontierCode results show Fable achieving comparable performance at roughly half the task cost, so it is probable developers could benefit from switching earlier than Anthropic recommends.

The post Anthropic built a model that beats Opus. It recommends Opus anyway. appeared first on The New Stack.