Claude Opus 5.5: Fable-Class Intelligence at 40% Lower Cost — What Changed for Builders
Anthropic shipped Claude Opus 5.5 on September 22, 2026. Fable 5.1-level performance at roughly 40% less running cost than Opus 5. Here's what changed for developers building on the Anthropic stack.
Anthropic shipped Claude Opus 5.5 on September 22, 2026. The headline is simple: Fable 5.1-level performance on most tasks at roughly 40% less running cost than Opus 5. But the details matter for anyone shipping on the Anthropic stack.
The Pricing Shift
Standard API pricing lands at $4 per million input tokens and $20 per million output tokens — a 20% drop from Opus 5's $5/$25. Cache reads fall from $0.50 to $0.20 per million tokens. The 40% typical-workload savings comes from both lower per-token rates and fewer tokens used per task.
A new Fast mode runs up to 2.5x faster at 2x the standard price ($8/$40), available on the Claude API and in Claude Code only — not on Bedrock, Google Cloud Vertex, Azure AI Foundry, or Claude Platform on AWS.
Four Breaking Changes from Opus 5
The migration guide lists four breaking changes that affect code already running on Opus 5:
-
Thinking cannot be disabled. Opus 5.5 always thinks. The
thinking: { "type": "adaptive" }parameter is now mandatory behavior, not optional. Requests that previously ran without thinking will now incur thinking tokens. -
Forced tool use returns an error. The pattern of forcing a specific tool via
tool_choice: { "type": "tool", "name": "..." }now errors. The model decides its own tool calls. -
Thinking blocks are tied to the model and conversation. You cannot swap thinking blocks between Opus 5.5 and other models, nor can you freely edit earlier context and replay preserved thinking. For API accounts created on or after August 31, 2026, replaying thinking after editing earlier messages can trigger errors.
-
Computer tool update on Claude API and Google Cloud. The
computer_20251124tool is replaced bycomputer_toolset_20260801with different response handling. Bedrock retains the old tool.
Preserved Thinking — The New Default
Opus 5.5 introduces preserved thinking: the model's reasoning blocks persist across turns and are billed once. This changes how you design multi-turn conversations. The thinking is tied to the specific model version and conversation — you cannot migrate thinking blocks to a different model or even a different Opus 5.5 conversation.
For developers, this means chat applications will feel slower on first reply because the model thinks at length before responding. System prompts that instruct thinking behavior now apply to the preserved blocks.
Fast Mode — Research Preview
Fast mode is a separate tier: up to 2.5x output speed for 2x the standard API price. It requires the speed: "fast" parameter with the fast-mode-2026-02-01 beta header on the Claude API. Temperature, top_p, and top_k must be removed from request payloads when using Fast mode.
This is a research preview — expect changes. It is not available on Bedrock, Vertex, Foundry, or AWS-hosted Claude Platform.
Migration Checklist
If you are moving from Opus 5:
- Remove any
thinking: { "type": "disabled" }or equivalent — thinking is now mandatory - Replace forced tool use patterns with prompt engineering or system instructions
- Audit conversation history handling: preserved thinking blocks from Opus 5.5 cannot be read by Opus 5 or other models
- On Claude API and Google Cloud, migrate
computer_20251124tocomputer_toolset_20260801 - Test model switching and fallback logic separately — thinking block incompatibility breaks naive fallbacks
- Update pricing calculations: $4/$20 standard, $8/$40 Fast mode, $0.20 cache reads
What This Means for MCP and Agent Builders
For developers building on MCP and the agent stack, Opus 5.5 changes the economics of agentic workflows. The 40% cost reduction on typical workloads makes multi-agent orchestration, extended reasoning chains, and high-tool-count servers more viable.
The preserved thinking feature aligns with the MCP 2026-07-28 spec's Multi Round-Trip Requests (MRTR) — both introduce stateful reasoning that persists across protocol turns. An agent that uses MRTR to gather input can now pair it with preserved thinking to avoid re-reasoning on each turn.
The breaking changes are real but manageable. The removal of forced tool use pushes toward better prompt design. The thinking mandate means you pay for reasoning on every turn — budget accordingly.
The Bottom Line
Opus 5.5 is the first model where Fable-class capability ships at Opus pricing. For teams that standardized on Opus 5 for cost reasons, the upgrade path is clear but requires code changes. For teams on Fable 5.1, the 40% savings on equivalent work is compelling.
The Fast mode preview signals where Anthropic is heading: latency as a tunable parameter, not a fixed model property. That matters for real-time agent interfaces and user-facing applications.
If this was useful, you can support my open-source work on Ko-fi or check out my services.