Claude Opus 5.5 Cuts Costs 40% and Ships With a Tighter Leash

What shipped, and the line most readers will skip

On September 22, 2026, Anthropic released Claude Opus 5.5, the first model of the Claude 5.5 family and, in Anthropic's words, "our first release since we called for pacing the frontier." The pitch has two halves: Fable-5.1-level performance on most work at 40% less than Opus 5, and the heaviest safeguards ever attached to an Opus model.

The second half is the one that changes how you run agents. Opus 5.5 ships with cyber, biology and distillation safeguards that "fall back to another model." On cybersecurity, the announcement is explicit: "most cybersecurity tasks will be re-routed to Opus 4.8." If your agent touches security work, part of it will be done by a model two generations older, and your eval suite needs to know that.

The pricing: what actually got cheaper

Anthropic's cost claim combines a lower per-token price with fewer tokens per task. The per-token part is easy to check:

The cache-read cut is the one that matters for agent loops. Anthropic itself notes cache reads "make up the majority of agentic and coding work costs," so a long-running coding agent with a stable system prompt and tool definitions gets most of its savings there, before any token-efficiency gain.

The headline 40% figure is Anthropic's own measurement "at default settings" on "typical workloads." Treat it as a claim to verify on your own traffic before it goes into a budget. Output generation is also more than 30% faster than Opus 5, per the same page.

The benchmarks: a clear lead, two exceptions

On CursorBench 4.0, Opus 5.5 at default effort scores 52.5% and beats GPT-5.6 Sol's top score (41.7%) by 11 points for about a third of the cost per task.

Two caveats from Anthropic's own page deserve quoting in full. First: "at these levels of capability we've found that benchmark margins have become a less reliable guide to real-world differences," and the gap with Fable 5.1 "is narrower than these scores suggest." Second, the Terminal-Bench 4.0 standard error is ±2.6 points for Opus 5.5 and ±3.5 to 5 points per model on Terminal-Bench-Science. The FrontierCode and AutomationBench margins are about one point either way: read them as ties.

The safeguard is already inside the scores

This is the part we'd read twice. Anthropic evaluated Opus 5.5 "with its production safeguards enabled." When they intervened, cybersecurity tasks were completed by Opus 4.8 and biology or frontier-LLM-development tasks by Opus 5. Anthropic says this "likely reduces Claude Opus 5.5's performance on these benchmarks."

The AutomationBench footnote goes further. Zapier ran those evaluations "without fallback models, so safeguard interventions were considered failures." The two losses in the table above therefore measure the safety layer as well as the model.

For a production team, that gives three concrete consequences:

• The same model can produce two different scores depending on whether your harness treats a fallback as a completed task or a failure. Decide which one you want before you compare Opus 5.5 with anything.
• Security-adjacent agents will be served by more than one model. Anthropic says routine bug finding and fixing stays on Opus 5.5, but "most cybersecurity tasks" move to Opus 4.8. The boundary between the two is the classifier's call, not yours.
• Your logs should record which model answered. If a fallback quietly produces a weaker patch, you want to see it in a dashboard before a customer sees it.

The escape hatch exists but is gated. Anthropic plans to expand its Cyber Verification Program to Opus 5.5 "in the coming weeks," with three tiers of increasingly permissive access. Security teams with a legitimate use case should apply now rather than discover the reroute mid-engagement.

First field reports point the same way

Within days of launch, a thread on r/ClaudeAI was titled "Claude Code keeps flagging harmless shell commands as cyber and downgrading me to Opus 4.8." The poster said the interruptions happened almost only inside Claude Code and suspected the classifier "over-reacts to anything that touches a shell."

One account is not a false-positive rate, and we haven't measured one ourselves. But it matches the mechanism Anthropic documents: an agent that runs shell commands all day produces exactly the kind of actions a cyber classifier is built to inspect. Separately, Anthropic says Opus 5.5 ships with "a classifier that screens every action before it runs" as part of its secure-coding stack, so shell-heavy agents plausibly sit where both layers are most active.

Where the efficiency claims come from

The efficiency story rests on vendor tests and early-access partners, none independently reproduced yet. Within that limit, the claims are specific:

• Codebase audit: an early tester audited and fixed a 200,000-line codebase in under three hours; Opus 5 took over 20 hours and 2.5x the tokens.
• HAProxy C-to-Rust rewrite (internal test): both Opus 5.5 and Fable 5.1 passed nearly all of HAProxy's regression tests; Opus 5.5 finished in 9.5 hours versus 12 and cost 51% less.
• Web performance: asked to cut load times on every page of an app, Opus 5.5 succeeded 39 of 40 times.
• Optiver: Opus 5 quality in about half the turns, time and output tokens, cutting that workload's cost by 40 to 50%.
• Lovable: builds finishing in "a third to half fewer steps."
• Kiro: more command-line tasks solved than Opus 5 with about 40% fewer calls and half the tokens.
• Deloitte Consulting: 72% of known bugs caught in code review at the lowest effort setting, against 56% for Opus 5 at high effort.

The pattern (fewer steps, fewer tokens, same or better output) repeats across GitHub, Quantium and Spotify quotes too. Quotes on a launch page are selected by the vendor, so the useful takeaway is the direction, and the specific workload types worth re-benchmarking: long migrations, audits and multi-file edits.

Anthropic also reworked the model's writing style after feedback on Opus 5: most important information first, less jargon, and closer adherence to the writing rules you give it. That's hard to benchmark, but for agents whose output a human reviews, it shortens review time.

What we're watching next

• Sonnet 5.5 and Haiku 5.5, announced for "the coming weeks" without dates or prices. Sonnet carries most agentic coding volume, so if the same safeguard class ships there, fallback behaviour stops being an Opus-only concern.
• The Cyber Verification Program rollout, and whether its tiers become available to ordinary engineering teams or stay limited to security vendors.
• Independent comparisons. Community tests are starting, such as a small Hacker News post pitting Opus 5.5 against Moonshot's Kimi K3 on the same coding task. Expect more of these before any third-party leaderboard settles the efficiency claims.

Our current recommendation: move cache-heavy coding agents to Opus 5.5 for the price cut, keep fallbacks visible in your logs, and re-run your own evals with safeguards on before trusting any published number. If you want help wiring that monitoring into your agent stack, get in touch.