Claude Opus 5.5 Launch

The headline number from Opus 5.5 isn't a benchmark score, it's a price cut. Anthropic dropped Opus pricing 20% to $4 per million input tokens and $20 per million output tokens, while cache reads fell 60% to $0.20 per million tokens ^[1]. Analysts tied the move directly to competitive pressure: Grok 4.7 has undercut Anthropic at $2/$6 per million tokens, and Xiaomi's open-weight MiMo-V2.6 has made a credible free alternative available, pushing Anthropic to compete on cost rather than just capability ^[2]. The result is a model that Anthropic says costs about 40% less to run for typical workloads than Opus 5 while performing at roughly the same level as the pricier Claude Fable 5.1 on most tasks ^[3]. For a company built on selling intelligence by the token, cutting the price of its top model just two months after the prior one shipped signals that efficiency, not raw capability, is now the more urgent competitive lever.

Ten days before Opus 5.5 shipped, Anthropic published 'We Must Pace the Frontier,' a framework about slowing AI development down ^[6]. The gap between that pledge and a rapid new release did not go unnoticed by commentators, who pointed to the model's very specific efficiency numbers as evidence Anthropic is racing, not pacing ^[6]. Anthropic's own framing leans on safety infrastructure rather than restraint: Opus 5.5 is the first Opus model to ship with safety classifiers similar to Claude Fable 5.1, paired with a pre-execution action classifier, an open-source sandbox, and mandatory code review before merges, which Anthropic calls its most secure coding agent yet ^[4]. The model also ships with zero data retention and a 'preserved thinking' anti-distillation safeguard that stops API users from editing Claude's prior context to extract its underlying reasoning ^[5]. Whether that constitutes pacing or just packaging speed with more guardrails is exactly the tension critics flagged.

Beyond benchmarks, Opus 5.5's release leaned on unusually large agentic runs to make its case: one tester completed a 680,000-line code migration in under a day, and a full port of HAProxy from C to Rust finished in 9.5 hours, 51% faster than Fable 5.1's 12-hour run on the same job ^[2][5]. A separate 200,000-line code audit that previously took over 20 hours dropped to under three ^[2]. Enterprise customer Box reported that switching production coding and analytics workloads to Opus 5.5 cut token usage by 63%, trimmed output verbosity by 42%, and ran about 30% faster than on Opus 5 ^[7]. Independent developers echoed the pattern outside official materials, with one engineer using the model to formally verify parts of an agent SDK with Lean and TLA+, producing over a dozen bug-fixing pull requests from a handful of prompts, while broader online reaction skewed toward enthusiasm about the model's efficiency and concise communication style, tempered by scattered worry that future updates could quietly dial back its current strengths.

One of Opus 5.5's headline improvements barely shows up in official benchmarks: its jump in 3D and vision-to-code tasks. Hands-on testing from the YouTube channel Codex Community showed Opus 5.5 building working Blender and Unreal Engine scenes and full website redesigns, complete with micro-animations and GSAP/Three.js interactions, from single prompts. The catch is speed: these tasks ran 40 to 60 minutes each, noticeably longer than equivalent jobs on prior Claude models, trading turnaround time for higher-fidelity, more complete output. That same tradeoff showed up again in the model's reception among hobbyist builders. A short prompt captioned 'Made entirely with Opus 5.5' set off a wave of Reddit users building full, unattended video-generation pipelines, with Claude Code orchestrating separate image- and text-to-speech models to produce finished videos end to end. Posters reported total API spend of around $4 per run, with pipelines running unattended for 1.5 to 2 hours before completion. Between the 3D/vision-to-code demos and the video-pipeline trend, the community reaction points to the same shift: Opus 5.5 is being used less as a chat assistant and more as an unsupervised creative operator, willing to spend extra wall-clock time producing finished, multi-step creative artifacts rather than quick text answers.

Opus 5.5 tops the Artificial Analysis Intelligence Index with a score of 58, several points ahead of GPT-6 Astra's 53, and generates output at roughly 91 tokens per second versus Astra's 61 ^[8]. On Terminal-Bench 4.0, Anthropic's own measurement puts Opus 5.5 at 66.4%, though an independent run from Artificial Analysis lands lower at 59.6%, still roughly on par with Astra ^[1][9]. But the lead is not universal: reviewers comparing the two models conclude Opus 5.5 is 'the better buy for coding agents and high-volume knowledge work,' while Astra 'is better for frontier math, science and abstract reasoning' ^[8]. That split, cheaper agentic throughput from Anthropic against Astra's reasoning ceiling, suggests the two labs are no longer competing on a single leaderboard but on different jobs entirely.