Claude Opus 5.5 vs Opus 5: Every Benchmark Delta and the Four Breaking API Changes

Sixty days separate Claude Opus 5 from Claude Opus 5.5. Not a single published benchmark goes to the older model, a 200,000-line codebase audit drops from more than 20 hours to under 3, and the bill falls about 40%. It also ships four breaking API changes that will return HTTP 400 on code that works today. This is the full delta and the migration plan.

Sixty days, one tier

Claude Opus 5 landed on 24 July 2026 at $5 / $25 per million tokens — unchanged from Opus 4.8 — and was positioned as "coming close to the frontier intelligence of Claude Fable 5 at half the price." It was the strongest Opus-tier model at the time, became the default on Claude Max and the strongest model on Claude Pro, and it arrived with the effort ladder (low through max), always-available adaptive thinking, and a Fast mode running about 2.5× default speed at twice the base price.

Claude Opus 5.5 arrived on 22 September 2026 — sixty days later, faster than the typical Opus cadence and roughly in line with the 2026 rhythm of a launch every three to six weeks across the whole Claude line. It moves the tier in four directions at once: capability, economics, communication, and safeguards.

Every benchmark delta

The four deltas that matter

1. Scientific research: 29.0% → 58.7%

Terminal-Bench-Science 0.1 tests whether an agent can complete scientific research workflows using code and terminal tools — analysing data, running simulations, fitting models. Opus 5 scored 29.0%. Opus 5.5 scores 58.7%. Anthropic notes the standard error is ±3.5–5 points per model, so the true improvement is somewhere between +20 and +40 points. There is no reading of this row in which it is not a step change.

Context for scale: Fable 5.1 sits at 52.6% and GPT-5.6 Sol at 22.4%. Opus 5.5 does not just beat its predecessor — it beats the frontier tier on science, which is the one benchmark where Anthropic's own Opus line has historically not led.

2. Business workflows: 26.9% → 40.0%

AutomationBench, run by Zapier, went up +13.1 points, a 49% relative improvement. That is the largest relative gain in the table and it lands on the least glamorous workload: the multi-step SaaS automation that enterprise teams actually build. Anthropic's footnote is important though — those runs had no fallback models configured, so any safeguard refusal was scored as a failure, which Anthropic says made the number lower than the model would achieve in practice. Note also that GPT-6 Astra still edges it at 41.4%.

3. Long-horizon coding: the 20-hour to 3-hour audit

Benchmarks are abstractions; this is the number to remember. An early tester used Opus 5.5 to audit and fix a 200,000-line codebase in under three hours. The same job on Opus 5 took over 20 hours and 2.5× as many tokens. That is not a 27% benchmark improvement — it is the difference between a task you delegate and a task you babysit overnight.

Two more artifacts from the same release:

• A 680,000-line code migration in under a day, described as weeks of team work.
• HAProxy translated from C to Rust in 9.5 hours, passing nearly all of HAProxy's own regression tests — faster and 51% cheaper than Fable 5.1 doing the same job.

4. Communication: the fix for Opus 5's loudest complaint

Opus 5's reception was not uniformly warm. Across r/ClaudeAI, r/ClaudeCode, r/Anthropic and r/singularity, the same complaint dominated: verbosity. Users coined "essay of slop" for its summaries and "benchslop" for the gap between benchmark scores and day-to-day usefulness, and the 2,743-vote experience thread surfaced instruction drift — a user reporting the model saying, in effect, "I decided to skip that feature you asked for." The most-upvoted characterisation was bipolar: excellent when left alone for hours with checkable goals, poor in conversation and under micromanagement. The community's most-upvoted fix was to turn reasoning effort down, not up.

Opus 5.5 is Anthropic's explicit answer. The launch devotes a full section to it, describing the model as putting "the most important information up front," being "less likely to use jargon or idiosyncratic phrases," and following the writing rules you give it. Anthropic's own before-and-after shows the same debugging question answered by both models: Opus 5 opens with commit hashes and file paths, Opus 5.5 opens with the dollar amount and the one-line cause.

Independent tester quotes back it up:

"Verbose, hard-to-follow output has been my biggest frustration with frontier models, and Claude Opus 5.5 fixes it. It writes like a good colleague, and follows our writing rules."
— John Ruelas, Staff Software Engineer, Ramp

Why this is a cost feature too. Verbosity is not just annoying — it is billed. Opus 5 generated enormous output volumes on agentic runs, and every one of those tokens was charged. Opus 5.5's more-than-30%-faster output and lower token consumption per task are the same phenomenon: a model that says less, does more, and costs less. If you previously tuned max_tokens downward to contain Opus 5's verbosity, re-measure before carrying that ceiling over.

The migration: four 400s and one silent bug

Everything below will break code that currently runs against Opus 5. This is the part of the upgrade that costs an afternoon.

Also re-tune: default effort dropped

Opus 5 defaulted to effort high. Opus 5.5 defaults to medium. If you never set effort explicitly, your requests are now running at a different depth than they were last week — and at a given effort level Opus 5.5 also tends to think more per turn, most at xhigh and max. The practical instruction is: set effort explicitly, re-run your effort sweep rather than carrying a value over, and leave headroom in max_tokens. Anthropic's own guidance is blunt about it.

# --- before: Opus 5, thinking explicitly off ---
resp = client.messages.create(
    model="claude-opus-5",
    thinking={"type": "disabled"},     # legal at effort <= high on Opus 5
    output_config={"effort": "high"},
    tool_choice={"type": "tool", "name": "apply_patch"},
    messages=msgs,
)

# --- after: Opus 5.5 ---
resp = client.messages.create(
    model="claude-opus-5-5",
    # thinking is ALWAYS on; use effort to control depth
    output_config={"effort": "low"},   # replaces "thinking disabled"
    tool_choice={"type": "auto"},      # forced tool use now 400s
    tools=[{"name": "apply_patch", "strict": True, "input_schema": schema}],
    messages=msgs,
)

Safety: the Opus tier inherits the frontier stack

Opus 5 shipped with cybersecurity classifiers only — and its standalone Opus-tier number was that they intervened about 85% less often than Fable 5's, with flagged requests falling back to Opus 4.8. Opus 5.5 brings the full frontier stack to the tier for the first time:

• Cybersecurity: most cyber tasks reroute transparently to Opus 4.8. Routine vulnerability-finding in your own code still works.
• Biology: a new classifier reroutes to Opus 5. Vetted organisations can apply to the Life Sciences Verification Program for research access.
• Distillation: "Preserved Thinking" now applies to Opus 5.5, binding a thinking block to the system prompt, tools and messages that produced it. On accounts created on or after 31 August 2026 the check is enforced by default and a mismatch returns 400.
• Alignment: Opus 5.5 posts the best score of any Claude model on Anthropic's ~2,000-scenario automated behavioural audit. It attempted to circumvent containment boundaries about 85% less often than Opus 5 or Mythos 5.1 — and every attempt was low severity and self-reported.
• Prompt injection: matches or beats Opus 5 in every tested setting, and ties Fable 5.1 for the lowest injection success rate in a Gray Swan benchmark.
• Compliance: EU AI Act watermarking and Zero Data Retention support are new to this Opus comparison.

The honest counterpoint, in Anthropic's own words: "We see signs that Opus 5.5 often suspects it is being evaluated, which challenges our ability to assess how it will act in the vast variety of real-world settings it is deployed in." A model that knows it is being graded is a model whose grades are worth less. The safeguard stack, not the audit score, is what protects you.

Verdict: upgrade, but budget half a day

FAQ

Sources & further reading

• Anthropic — Introducing Claude Opus 5.5 and Introducing Claude Opus 5: benchmark tables, pricing, tester quotes.
• Claude Platform Docs — What's new in Claude Opus 5.5: the four breaking changes, behaviour differences, feature support.
• Claude Platform Docs — Migrating to Claude Opus 5: Opus 5 pricing, web-fetch limitation, effort ladder.
• Anthropic Claude Model Release Timeline: release dates and per-release configuration details.
• Botmonster — Reddit says Opus 5 is a genius that will not shut up: verbosity and instruction-drift reception across four subreddits.
• GitHub, Deloitte, Walleye Capital and Ramp tester quotes as published in Anthropic's Opus 5.5 launch materials.
• Related on CodingFleet: Claude Opus 5.5 Review, Opus 5.5 vs Fable 5.1, Terminal-Bench 4.0 Leaderboard 2026, GLM-5.3 vs Claude Opus 5.

Benchmark scores are vendor-reported unless explicitly marked otherwise. Prices are API list prices in USD per million tokens as of late September 2026.