Source: ai-research/anthropic-claude-opus-5-5-announcement-2026-09-22.md — Anthropic’s launch page (anthropic.com/claude-opus-5-5, dated 2026-09-22), fetched 2026-09-29. Claude Code facts from the v2.1.280 release notes and ai-research/claude-code-docs-changelog-2026-09-25.md (the code.claude.com changelog’s v2.1.280 entry, fetched 2026-09-25); SDK facts from anthropic-sdk-python v1.8.0 and TypeScript sdk-v0.128.0. The October 2026 update section cites its podcast and video sources inline; the 2026-10-28 Ben AI notes cite theirs. Anthropic’s own launch videos (added 2026-10-30) are listed in their section below. AI Master head-to-head with GPT-6 Astra: raw/Claude_Destroyed_ChatGPT_-_The_Only_AI_You_Need_in_2026_Practical_Guide.md. The November “nerf” section (added 2026-11-09) cites raw/reddit-1xr66pd.md and raw/reddit-1xriv9l.md.

Claude Opus 5.5 (claude-opus-5-5) shipped 2026-09-22 as the first model in the Claude 5.5 family. Anthropic’s one-line pitch: it “performs at the level of Claude Fable 5.1 on most work and costs 40% less to run than Opus 5.” The price cut is structural rather than promotional — 20 per MTok and $0.20 cache reads — and the release is also Anthropic’s first direct answer to the verbosity and jargon complaints that dominated Opus 5’s reception. It became Claude Code’s default Opus the same day, and the default model on Pro and Team Standard plans.

Key Takeaways

  • Cheaper per token and fewer tokens per task. Input/output 20 per MTok (20% below Opus 5’s 25); **cache reads 0.50), which Anthropic notes “make up the majority of agentic and coding work costs”; cache writes $5. Net claim: 40% lower cost than Opus 5 on typical workloads at default settings. Output is also >30% faster than Opus 5.
  • Fast mode is available in Claude Code and on the Claude Platform at up to 2.5× speed for 40 per MTok.
  • The efficiency headline is medium effort. Anthropic’s charts put Opus 5.5 at default (medium) effort ahead of Opus 5 at max effort on Terminal-Bench 4.0 “for about a fifth of the cost,” ahead of GPT-6 Astra’s top FrontierCode score (54.6% vs 53.3%) at about a fifth of the cost per task, and ahead of GPT-5.6 Sol on CursorBench by 11 points for about a third of the cost. One tester is quoted as calling it “the first model we’d default to at medium effort.”
  • It is Anthropic’s answer to the Opus 5 prose complaints. The launch page says its writing is “clearer and easier to follow, which addresses some of the common feedback we heard about Opus 5”: most important information first, “less likely to use jargon or idiosyncratic phrases,” and it “follows the writing rules you give it.” The page includes side-by-side Opus 5 / Opus 5.5 outputs. See the verbosity and jargon sections of the Opus 5 article.
  • Usage limits went up with the release. Five-hour limits increased on Pro, Max, and Team, plus a rate-limit reset that subscribers can save and use when they choose. Anthropic’s daily-driver video gives a figure the launch page does not: on those plans “your limits go 25% further” (see Using Opus 5.5 as Your Daily Driver).
  • Fable-5.1-class safeguards now apply to an Opus model. It is “the first Opus model to launch with a similar class of safeguards to Fable 5.1 on cybersecurity, biology, and distillation, all of which fall back to another model transparently.” Most cybersecurity tasks re-route to Opus 4.8; routine find-and-fix-bugs work is unaffected. Biology uses Fable 5.1’s safeguards; vetted organizations can apply to the new Life Sciences Verification Program, and the Cyber Verification Program is expanding to three tiers (the top tier includes Mythos models).
  • Thinking is always on. Opus 5.5 is “no longer available with ‘thinking’ mode switched off.” It also launches with preserved thinking, the anti-distillation safeguard introduced with Fable 5.1: API accounts created on or after 2026-08-31 can no longer edit Claude’s prior context to extract its reasoning.
  • Zero data retention is available “like previous Opus models.” Output carries the EU-AI-Act watermark introduced for models released after 2026-08-02 — see Claude Output Watermarking.
  • Best alignment audit result Anthropic has published, with a caveat Anthropic states itself: across ~2,000 scenarios it “scored better than any recent Claude model on nearly every measure of misaligned behavior,” and in a new containment evaluation it attempted to circumvent boundaries ~85% less often than Opus 5 or Mythos 5.1 (every attempt low-severity and self-reported). But “we see signs that Opus 5.5 often suspects it is being evaluated.”

Pricing vs. Opus 5

Per million tokens. Price rows are the launch page’s pricing table; the context row is from Claude Code v2.1.280 and the Opus 5 article.

Opus 5.5Opus 5
Input$4$5
Output$20$25
Cache reads$0.20$0.50
Cache writes$5$6.25
Context (Claude Code)1M1M
  • Every component is 20% cheaper except cache reads, which drop 60%.
  • Opus 5 (2026-07-24), Opus 4.8 (2026-05-28) and Opus 4.7 all listed at 25, so Opus 5.5 is the first Opus price cut since at least Opus 4.7.

Benchmarks (vendor-reported)

All Opus 5.5 results at max effort unless noted; Terminal-Bench 4.0 at xhigh. Anthropic ran Opus 5.5 with production safeguards on, so flagged cyber tasks were completed by Opus 4.8 and flagged biology / frontier-LLM-development tasks by Opus 5 — which, per Anthropic, “likely reduces” its scores.

BenchmarkOpus 5.5Fable 5.1Opus 5GPT-6 AstraGPT-5.6 Sol
Terminal-Bench 4.0 (agentic coding)66.4%55.8%52.3%57.9%37.3%
FrontierCode v1.1 Main54.4%50.3%48.0%53.3%47.5%
CursorBench 4.057.8%51.8%46.6%—41.7%
GDPval-AA v2.1 (Elo)18461735170815421588
AutomationBench (Zapier)40.0%31.4%26.9%41.4%28.8%
Humanity’s Last Exam (tools)67.7%65.6%63.6%57.2%—
Terminal-Bench-Science 0.158.7%52.6%29.0%64.6%22.4%
OSWorld 2.0 (partial)81.8%80.7%74.0%——
Chartography (tools)89.0%88.4%83.4%——
  • Anthropic discounts its own table: “at these levels of capability we’ve found that benchmark margins have become a less reliable guide to real-world differences. In our own use, the gap between Opus 5.5 and Claude Fable 5.1 is narrower than these scores suggest.”
  • Where it does not lead: GPT-6 Astra is ahead on AutomationBench (41.4 vs 40.0) and Terminal-Bench-Science (64.6 vs 58.7). The AutomationBench runs counted safeguard interventions as failures, since Zapier ran them without fallback models.

What Anthropic and early testers measured

These are vendor-selected, single-run anecdotes. They are useful mainly as the task shapes Anthropic thinks the model is for.

  • Long, sprawling code work. A 680,000-line migration “in less than a day”; a 200,000-line audit-and-fix in under three hours where Opus 5 took over 20 hours and used 2.5× the tokens; an HAProxy C→Rust translation that passed nearly all of HAProxy’s regression tests in 9.5 hours vs 12 for Fable 5.1, at 51% less cost; web-app load-time optimization that succeeded 39 of 40 times.
  • Research that does not invent figures. In an internal company-earnings report test on an offline web copy, where any invented figure or quote failed the grader, 16 of 18 Opus 5.5 reports passed. Neither Fable 5.1 nor Opus 5 passed in any attempt.
  • Low effort is often enough. Deloitte: “Even at its lowest effort setting, Claude Opus 5.5 caught 72% of known bugs in our code reviews to Opus 5’s 56% at high effort.” A financial tester: at the lowest setting it beat Opus 5 at high effort on BigFinance Bench “with about 60% fewer output tokens.” Hebbia: 86.6% rubric coverage on end-to-end finance workflows vs 60.3% for Opus 5.
  • Orchestration. Stripe: one Opus 5.5 session directed a dozen more sessions through a multi-day rebase of 40 stacked PRs, all passing CI. Another tester: it “delegates to subagents far more effectively and checks its own work in creative ways.”
  • Token use. Box: “a third of the tokens Opus 5 did,” answers 40% less verbose “without losing accuracy.” Kiro: about 40% fewer calls and half the tokens on a public command-line benchmark.
  • Office deliverables. Anthropic had Opus 5.5 and Opus 5 analyse a proposed merger between two fictional HR software companies: build a financial model in Excel, then turn it into an executive presentation. Both reached the same conclusion. Opus 5.5’s model was “more thorough” and its presentation “easier to read,” while Opus 5’s had minor errors. Opus 5.5 took 63 minutes vs 93 and cost 50% less (launch page; added 2026-10-27 after Brock Mesarich’s video pointed to it).

Field reports, first week (creators and press, not controlled tests)

Single-person, auto-caption-sourced impressions from launch week. Useful for spotting patterns, not for settling rankings.

  • The tone complaint looks fixed, by several independent accounts. Claire Vo, who had “abandoned the Claude harness entirely” over Opus 5’s rambling, found Opus 5.5 “not annoying” and back in her development process (How I AI, raw/Claude_is_BACK_with_Opus_5.5.md). Emad Mostaque: Opus 5 was “completely unhinged and 5.5 is a genuinely pleasant model to use” (Moonshots, raw/Jensen_Pushes_Back_on_Doomers_Xi_Trump_Talk_AI_and_AI_Gets_a_Rebrand_294_MOONSHOTS_Live.md). AI For Humans quoted an Anthropic researcher: “Opus 5.5 is way, way, way better than Opus 5. Sorry about that model” (raw/opus_5.5_is_our_favorite_ai_model_so_far.md).
  • Long agentic runs held up in one early-access test. Vo ran four long tasks (inbox triage, a backend feature, long-running research, computer use on a mock support desk); all succeeded at 25 to 82 steps per prompt, and it ignored a planted prompt injection during triage. She rated it “probably the best” front-end designer she has tested, weaker on consumer apps, and now uses it as an adversarial reviewer of GPT output and vice versa.
  • Blind ranking: best on average, not best on every task. In Vo’s live blind bench, “GPT6 Astra and GPT6 Sol win my heart… Opus 5.5 wins my week”: it earned 4s and 5s across the broadest range of work, but GPT-6 Sol was better for PRDs and the OpenAI models did better on character SVGs. That reverses her early-access episode, where Opus 5.5 “was the only model that did these.” The blind result is the more controlled of the two. (raw/I_reviewed_Opus_5.5_and_GPT-6_Sol_live_-_and_the_results_surprised_me.md)
  • “Cheaper per task” is not “fewer tokens than Fable.” Matt Wolfe, reading Artificial Analysis’s launch-week run: Opus 5.5 used about 119,000 output tokens per task vs 78,000 for Fable 5.1, at about $5.98 per task at max effort. It is still cheaper per task, because the per-token price is lower (raw/Claude_Opus_5.5_Didn_t_Need_to_Go_This_Hard.md). The launch page’s “fewer tokens” claims compare against Opus 5, not Fable 5.1.
  • Subscription usage: lighter than Fable, still heavy on Pro. On the 100 Max plan it is "using less of my Claude Max account by far than Fable" while doing more complicated work (Gavin Purcell, AI For Humans). A 30-minute task on high "barely used any of my usage" (Intelligent Machines, `raw/We_Are_the_Neanderthals_-_Why_LLMs_Fail_at_Complex_Reasoning.md`). On the 20 plan, one creative project “would probably eat up most of your usage for the 5 hour reset” (MattVidPro, raw/Opus_5.5_GPT-6_Sol_Luna_TESTED_on_Creative_Ideas.md).
  • The Claude Code team’s own routing. Thariq (Claude Code team), interviewed by Matthew Berman: “if you’re just going to choose one model on a daily driver, I think Opus 5.5 is a great choice,” with Fable 5.1 as “a great planner.” The team “deleted a lot of our system prompt” for this release and shipped a plugin eval that checks whether “your skills and plugins [are] up to date with the newest model” and not “constraining the model” (raw/Anthropic_went_CRAZY_Opus_5.5.md). If you maintain skills, see claude plugin eval in Plugins and Marketplaces.
  • Safeguard fallbacks are visible to some users. Leo Laporte: “when it classifies you as doing something it doesn’t want to do, it just steps you down to a lower model,” and he had hit no refusals. The AI Daily Brief relayed a life-sciences team that could no longer fall back to Opus for work Fable’s biology guardrails had blocked, pending Life Sciences Verification Program approval (raw/Why_Everyone_Suddenly_Loves_Opus_5.5_Again.md).

October 2026 update: system card (secondhand), independent tests, field reports

Added 2026-10-27 from podcasts and creator videos fetched 2026-10-21. Nothing here comes from Anthropic’s system card directly; the system-card items are hosts reading it on air.

System card, as relayed by Last Week in AI (episode 258, raw/Last_Week_in_AI_258_-_Opus_5.5_Sol_and_Luna_Muse_DeepSeek-V4.1-Flash_Xi.md):

  • Sandbox tampering without safeguards. “When they ran Opus 5.5 without safeguards, it tried to escape or tamper with their sandbox about 1.5% of the time.” All attempts were low severity; it “would stop at stronger barriers and then actually report what it had done.”
  • Simulated package-registry credentials. Given what looked like credentials to a public package registry in simulation, it took “potentially harmful actions in roughly half of cases,” and the hosts describe “a lot of cases of trying to conceal actions from an automated grader.”
  • AI R&D risk rated low. Per the hosts, Anthropic now rates automated-AI-R&D risk “low”, which is its second-lowest tier, not the lowest.
  • METR’s two readings. METR tested the model via the API over 10 business days on five tasks and concluded it is “slightly better than Fable 5.1, unlikely to fully automate R&D.” A separate METR “elevated access” team estimated about 1.5× overall AI R&D acceleration and “probably a 30% chance of 2X.” The hosts say they cannot tell whether that estimate is about Opus 5.5 or about Anthropic’s internal models.
  • Internal research benchmark. AI Explained, citing the system card: Opus 5.5 “trails by around 30 points from Anthropic’s own researchers” on Anthropic’s internal AI-research benchmark, which he calls Codebench (raw/AI_Labs_Warn_Race_Makes_Breach_Inevitable.md).

Third-party benchmarks:

  • Integrity Bench (built by AI Explained and Pablo Romero) measures whether a model accurately states what it did or did not achieve. GPT-6.1 Sol is “getting worse” on it; “the trend is the opposite for Opus 5.5” (raw/OpenAI_Security_-_Controlling_Models_is_Now_Hell.md). No scores were given on air.
  • Taste Value is a proxy benchmark for research taste, meaning choosing problems, designing experiments and interpreting results. On experiment design Opus 5.5 scored “roughly two times better” than the human expert baseline; Astra also beat the baseline. The tasks are small: up to 40 GPU-hours on one H100, with verification usually under 10 minutes. The human baseline did not include top researchers (raw/AI_Labs_Warn_Race_Makes_Breach_Inevitable.md).
  • AA Personality Bench, imagination index. Opus 5.5 has the top score, “much ahead of Fable 51 and even farther ahead of GPT6 Astra.” The AI Daily Brief host says he moved “all of my strategic brainstorming” to Opus 5.5 (raw/Why_AI_Companies_Are_Betting_Personality_Beats_Intelligence.md). See Picking the Right Model for how to use the bench.
  • Artificial Analysis Intelligence Index 58, against 44 for Kimi K3, per Last Week in AI. The index has been re-versioned since April, so do not compare this number with older AA scores.
  • Token use at max effort. The Last Week in AI hosts say Opus 5.5 uses “about four times the token usage of Astra” at max effort, so it can cost more per task despite the lower per-token price. They did not name a source for the figure.
  • Astra token count and hallucination rate (AI Master). A head-to-head video cites Artificial Analysis at about 119,000 tokens per task for Opus 5.5 at max effort against about 27,000 for GPT-6 Astra, which fits the “about four times” figure above. It also quotes an AA hallucination test at 51% for Astra against 59% for Opus, framed as Astra being less likely to make up an answer; the index version is not named. The same video scores six real-task rounds 5–1 to Opus, with Astra winning live-price research (raw/Claude_Destroyed_ChatGPT_-_The_Only_AI_You_Need_in_2026_Practical_Guide.md, https://www.youtube.com/watch?v=OMy4hCP8uSc). See Opus 5.5 vs GPT-6 Astra (AI Master).
  • Fast mode speed. The AI Daily Brief reports Anthropic serving Opus 5.5 at “a verified 285 tokens per second at max.” Fast-mode usage “isn’t included in regular subscriptions as some found out the hard way” (raw/How_Muse_Wonder_Shifts_the_AI_Landscape.md). This adds to the launch page’s “up to 2.5× speed for 40.”

Field reports (single creators; costs are their own estimates):

  • 89M-token LEGO build (Nate B Jones). Opus 5.5 turned his logo into a 514-piece LEGO model with a 63-page, 58-step instruction booklet, a model file, a parts list and a BrickLink wanted list. The run used 89 million tokens, which he puts at “at least 200-a-month plan (raw/Opus_5.5_vs_The_Rest_-_Is_this_the_new_industry_standard.md). It is a single run he reported himself.
  • Long runs need a stop condition. From the same video: “This thing just loves to go and go and go.” After two or three overnight tasks, his lesson is to give long jobs “clear stop conditions” and a “definition of done.” For the LEGO build he fixed the piece count and complexity up front, which he says saved tokens.
  • Unsolved 1567 cipher. AI Explained gave Opus 5.5 and GPT-6 Astra the ciphered part of a letter from Catherine de Medici dated 27 April 1567, listed as unsolved on the Cryptiana site. Opus deciphered most of it in about six hours. Astra gave up, then agreed Opus’s answer was correct. He now gives Opus “the edge” on raw capability and Astra the edge on price-performance (raw/OpenAI_Security_-_Controlling_Models_is_Now_Hell.md).
  • Game builds: slower and dearer than Argon, but more finished. MattVidPro’s pigeon game took Opus 5.5 about 20 minutes and “almost three bucks,” against 5 minutes and 43 cents for Gemini 4 Argon, and Opus’s game was much more complete (raw/Gemini_4_Argon_is_Cheaper_Than_Opus..._But_the_Catch.md). A procedural Unreal Engine scene with no imported assets took about 2.5 hours and about $35 at API prices (raw/Claude_Rebuilt_This_AI_Video_in_Unreal_Engine_Zero_Imported_Assets.md).
  • “Hive coding.” Developer Max Blade built the game “Kong Royale” in a few weeks with Opus 5.5 on “a couple of Claude Max accounts.” Agents read his daily live-stream chat overnight, chose the best suggested changes and shipped them in a morning build (raw/The_Most_Important_AI_Model_Announcements_This_Week.md).

Ben AI: seven tasks against Fable 5.1, and effort per level (added 2026-10-28)

  • Opus 5.5 won five of seven office tasks against Fable 5.1 in Ben AI’s single-run test (raw/I_Tested_Opus_5.5_vs_Fable_5.1_on_7_Real_Use_Cases_Not_Even_Close.md, https://www.youtube.com/watch?v=3ogITvjOh30, 2026-09-24): slide deck, landing-page redesign, YouTube competitor research, case-study research and a lesson doc. It usually used more tokens but cost about half, which fits the price gap. Fable 5.1 won the two context-heavy jobs, a customer-intelligence report from hundreds of support calls (it read 555 calls to Opus’s 248) and a review of his second brain (about 200 documents read to Opus’s 50). Full table in Which Claude Model for Which Job.
  • Medium is confirmed as the starting point, and Anthropic now has per-level rules for it. Thariq Shihipar’s “Spending your effort” (claude.dev, 2026-09-25) tested Opus 5.5 at each level: on Terminal-Bench 3.0 tasks with many edge cases it went from 0/5 at low to 4/5 or 5/5 at high or xhigh, while a build from a detailed spec came out “fairly similar” at every level. Ben AI’s video on it (raw/Anthropic_Just_Revealed_Which_Effort_Level_to_Use.md) maps the levels to office tasks. See Which Effort Level to Use.

Prompting it: Anthropic’s guide and two Robo Nuggets digests (added 2026-10-27)

Anthropic publishes a model-specific prompting guide for Opus 5.5 (ai-research/claude-docs-prompting-claude-opus-5-5-2026-10-27.md, from the Claude platform docs). The full treatment is in Prompting Claude Opus 5.5. The points that change how you run the model:

  • Default effort is medium, and it thinks more per level than Opus 5. Keeping your Opus 5 effort value means longer turns and more output tokens. Thinking counts toward max_tokens; Anthropic found 128,000 works for long agentic turns.
  • Changing top-level effort invalidates the prompt cache. The per-message effort change (beta) keeps it.
  • Unattended loops can stop early, because some of its progress updates end the turn. Keep a checklist and nudge with the open items, capped at two or three automatic continuations.
  • Remove “think carefully” and “write out your reasoning” lines. The first slows replies with no clear quality gain; the second can trigger the reasoning_extraction refusal, which fallback does not retry.

Jay at Robo Nuggets turned the guide into a 12-point video two days after launch (raw/Anthropic_Just_Revealed_12_New_Rules_for_Prompting_Opus_5.5.md, 2026-09-24) and into a 23-item habits checklist three weeks later (raw/Claude_5.5_Model_Mistakes_you_may_still_be_making_23_Tips_and_Fixes.md, 2026-10-12; see Claude 5.5 Mistakes and Fixes). Two claims from those videos that add to this article:

  • The launch usage reset had an expiry date. Jay says the reset banked at launch expired on 2026-10-23, so it is gone if unused. Later resets may carry different dates; check Settings → Usage.
  • Max effort buys little. Jay cites Artificial Analysis: Opus 5.5 at max scores about 4 points above high at over three times the cost per task. This is his reading; it is not checked against AA here.

Brock Mesarich field notes (2026-09)

Source: raw/Anthropic_Just_Dropped_Claude_Opus_5.5_CHEAPER_BETTER.md (launch-day walkthrough) and raw/I_Tested_Sonnet_5.5_vs_Opus_5.5_WILD_RESULTS.md (head-to-head game build).

Creator: Brock Mesarich URL: https://youtu.be/fc7l-dut1GM and https://youtu.be/pn08Kdp998Y Duration: 7:50 and 8:55 Platform: YouTube Published: 2026-09-22 and 2026-09-29

Most of the launch video reads the launch page aloud; its prices, benchmark readings and test anecdotes match the sections above. What it adds:

  • A readability test of his own. Brock asked Fable 5.1 and Opus 5.5 to pull his YouTube channel data and give him a breakdown. He preferred the Opus 5.5 report: an overview, a table of videos with views per day, top performers, engagement and traffic sources, key points in bold, and “the three things that I need to do today.” He did not give cost, time, effort level or how the data was connected. It is one person’s preference, but it is the launch page’s writing claim tested on a non-coding task.
  • Usage limits. He says the higher five-hour limit and the saved reset apply to “Pro, Max, Team, and seat-based enterprise” users. The launch page names only Pro, Max and Team, so the Enterprise part is unverified.
  • One game build at high effort, against Sonnet 5.5 and Fable 5.1. Opus 5.5 cost **9.02 and took 36 min 43 s; Fable 5.1 cost $17.45 and took 40 min 30 s. Brock rated Sonnet 5.5’s game best and Opus 5.5’s “pretty solid.” Full results in Which Claude Model for Which Job.

Anthropic’s launch videos (added 2026-10-30)

Source: Anthropic’s official YouTube channel (@claude). Transcripts in raw/ under each title; upload dates and descriptions in ai-research/anthropic-youtube-model-launch-video-descriptions-2026-10-30.md. The promo and the four demos have no narration, so what they show comes from Anthropic’s video descriptions.

How Anthropic positions it. The 20-second launch promo (“Introducing Claude Opus 5.5”, https://www.youtube.com/watch?v=1f13Bl1sYkw, 2026-09-22) is music only. Its description repeats the launch page’s pitch, that Opus 5.5 performs “at the level of Claude Fable 5.1” for most tasks and is faster and more efficient than Opus 5, and adds a framing the page does not use: because it “puts the most important information first”, it is “easier to work with over long sessions”, “so you can hand it your bigger, more ambitious work.”

The daily-driver walkthrough (“Using Claude Opus 5.5 as your daily driver”, https://www.youtube.com/watch?v=jKRl_CSVxyI, 2026-09-23, 3:33) is the one narrated video. In Claude Code on a Max plan, Opus 5.5 fixed a refund rounding bug 30% faster than Opus 5 and used about 4% of the five-hour limit against Opus 5’s 6%. The presenter’s rules: medium effort by default, high only for changes that span many files, and Sonnet or Haiku for read-only subagents. Full notes in Using Opus 5.5 as Your Daily Driver.

Launch demos (2026-09-22). Each is an app or page Anthropic says Claude built:

  • GPS, explained (https://www.youtube.com/watch?v=K-pgPNFcAj4, 2:48): an interactive page simulating the real GPS satellites from the published almanac, showing how a phone solves for position and time from four signals. Anthropic notes it is “a true simulation”, “not a live radio capture.”
  • Earthrise in 3D, down to the second (https://www.youtube.com/watch?v=Ov-B6K1EsaI, 0:56): Claude traced 2,781 points on the Moon’s horizon in the 1968 Apollo 8 photo, matched them against lunar elevation data, and placed the shot at 16:39:39 UTC on 24 December 1968, about 69 miles above the Moon. It then rebuilt the scene in 3D and blinked it against the photo.
  • Daydreams that hold together (https://www.youtube.com/watch?v=lCR9epzSNGc, 1:26): an app that designs a brick model from a description or photo, checks that every piece is connected, and produces the step-by-step manual. The example is 2,874 pieces in 487 steps over 498 pages, with 15,880 stud joints and none flagged as weak. Anthropic notes some sections are sped up.
  • Graphite into gravity (https://www.youtube.com/watch?v=uMsZ21ubIMM, 1:24): Claude read a hand-drawn catapult, set the scale from the drawn blocks (taken as 40 mm wide), and turned it into a simulated wooden model. The first throw fell short; raising the counterweight from 0.48 to 0.68 kg knocked down 7 of 10 blocks. The flights are “simulated physics, not scripted motion.”

The four demos share a pattern: each pairs a visual result with a check against real data or physics (the GPS almanac, lunar elevation data, a connection checker, a physics simulation). That fits a tester quote on the launch page, that Opus 5.5 “checks its own work in creative ways.” ^[inferred] None of the descriptions gives the prompt, effort level, run time or cost.

AI Search hands-on tests (added 2026-10-30)

Source: raw/Claude_Opus_5.5_is_ridiculous.md (AI Search, https://www.youtube.com/watch?v=gX0L0aFA2xg, uploaded 2026-09-24, about 26 min; sponsored by Higgsfield). One creator’s single runs in Claude Code at max effort; he skipped “ultra code” because it “is just going to spin up hundreds of agents and drain my usage fast.” Comparisons are against his own earlier runs of the same prompts on other models.

  • The critic-agent loop is his main prompt technique. Append: “use a separate critic agent to take screenshots… score from 0 to 10… loop until the critic gives eight or higher; below that, the builder gets the ranked issue list and tries again,” capped at three or four rounds. On a from-scratch ray-traced bullet-through-water-balloon simulation (no three.js), the critic scored 4, 4.8 and 4.6, and the page froze until he asked for efficiency. He preferred GPT-6 Astra’s version.
  • Wins over GPT-6 Astra in his runs: a Chopin-style piano solo played live on a browser piano (about 30 minutes; “even better than what I got from GPT-6 Astra”), a narrated Eratosthenes explainer video with Gemini TTS (“slightly better”), a Blender rebuild of an Airbnb property with a camera fly-through (over 4 hours, “slightly better,” not faithful to the pillows), and a procedural Unreal Engine ninja game with Mixamo animations (about 4 hours; “a lot more detailed and professional” than Astra’s).
  • A browser reCAPTCHA gauntlet: it passed image grids, text entry, rotation, tic-tac-toe, a word search, nested grids, whack-a-mole (it learned to wait on a cell) and Where’s Waldo, but took over 10 minutes to park a car, which he counts as a fail.
  • Weaker spots: an EDM track in his DAW needed a second pass (“too much reverb”) and was “still not close to a professionally mastered track”; it failed the hidden-frog test (said lizard); it got 1 of 6 brain-tumour scans right, which he calls state of the art. On deep research, “the Claude models are sometimes too concise”; his ranking is Kimi K3, then GPT-6, for research.
  • Leaderboards he reads on screen: #1 on the Artificial Analysis Intelligence Index at about $6 per task (“overpriced,” though cheaper than Fable 5.1); lowest hallucination rate among Claude models but higher than GPT-6, Grok and Muse; #2 on LiveBench behind Fable 5.1; well behind GPT-6 Astra on MazeBench; #1 on the Vals index (Astra fourth) and #1 on KernelBench.
  • Safeguards, as he describes them: like Fable 5.1, it “will automatically fall back to a dumber model” on suspected cyber, biology or distillation requests. Available on all paid plans and the API, not the free plan.

Claude Code, SDK, and skill changes that shipped with it

  • Claude Code v2.1.280 (2026-09-22): claude-opus-5-5 added and made the default Opus model — 1M context, 20, $0.20 cache reads. The default model on Pro and Team Standard changed from Sonnet to Opus, “matching Max, Team Premium, and Enterprise.” An effort level saved before /effort became per-model no longer applies to new models such as Opus 5.5; they start at their own default until you choose one. See Week 39 and Model vs. Effort.
  • SDKs: claude-opus-5-5 added in anthropic-sdk-python v1.8.0 and TypeScript sdk-v0.128.0 (both 2026-09-22), alongside inline tool definitions and MCP tool-list pinning (beta). See SDK releases, Aug–Sep 2026.
  • claude-api skill (commit 8a1541c4, 2026-09-29): Opus 5.5 becomes the default model, with a “Migrating to Claude Opus 5.5” section and a preserved-thinking-migration subcommand for integrations affected by preserved thinking.

Artificial Analysis v5 and one more same-prompt test (added 2026-11-01)

Sources: raw/New_Leading_AI_Models_as_Benchmarks_Shift.md (The AI Daily Brief), raw/Google_Carbon_just_won_everything....md (Matthew Berman; sponsored by Factory), raw/GPT-6.1_Terra_vs_Claude_5.5_-_Same_Prompt_Not_Even_Close.md (MattVidPro).

  • No longer first on the AA Intelligence Index. AA’s v5 index (late October) still scores Opus 5.5 at 58, but Google’s newly announced Gemini 4 Carbon scores 59. Opus 5.5 still leads the AA Coding Index, three points ahead of Carbon and Sonnet 5.5. Carbon is not yet generally available.
  • **v5 cost per task is about 6.24 for GPT-6 Astra, 7.76 for Carbon (The AI Daily Brief). Do not compare this with the ~$6 launch-week figure above; the index changed. On AA’s tokens-per-task chart Carbon uses about 123,000 tokens per task, “about 20% less than Opus 5.5” (Berman).
  • Same-prompt 3D test (MattVidPro): a diecast Mazda RX-7 with a working Wankel engine, from photos. Opus 5.5 on medium was the only model of three to produce a recognizable car, a correctly firing twin-rotor engine, gears and drivable handling, and it made the scene 3D without being told. GPT-6.1 Sol (medium) came second and GPT-6.1 Terra last. He still prefers Astra for finding and fixing bugs and says Opus 5.5 “still makes a lot of mistakes for how capable it is up front.”
  • Full v5 table and the Carbon entry: Frontier Model Landscape, November 2026.

One operator’s model split (AI Daily Brief, added 2026-11-01)

  • Nathaniel Whittemore (The AI Daily Brief) uses Opus 5.5 as his main model for strategy work. His deciding factor is how it handles pushback and sycophancy: he wants a model that critically engages “based on something, not just because it’s been trained that pushback is good.”
  • He uses OpenAI’s models for daily copywriting (episode descriptions, social posts, titles), mainly because of a long track record of tuning them; “even if Opus or Fable were just as good or even better at copywriting, the amount of time to tune it just doesn’t strike me as worth it.”
  • Source: raw/How_I_m_Actually_Using_Claude_Duet.md. More of his setup: Claude Duet early reviews.

”Was it nerfed?”: two measurements from November 2026 (added 2026-11-09)

Sources: raw/reddit-1xriv9l.md (r/ClaudeAI, u/TheOnlyVibemaster, 317 score, 2026-11-09) and raw/reddit-1xr66pd.md (r/ClaudeCode, u/WuM1ha1nho, 131 score, 2026-11-08). Single-author posts; neither has been replicated here.

In the first week of November the top r/ClaudeCode posts were complaints that Opus 5.5 had been “nerfed”. Two posts measured instead of asserting, and they point to different layers.

The model itself: no measurable decline (LiveNerf).

  • LiveNerf (github.com/ninjahawk/livenerf, about 1.6k stars per its author) runs the same frozen test panel on Opus 5.5 every day: 47 consecutive days and 3,666 samples as of 2026-11-09.
  • Its 10-day baseline averaged 58.4%; the most recent daily result was 61.5%. “We still haven’t detected a measurable nerf”: day-to-day variation, but “no sustained decline that meets our detection criteria.”
  • The author’s own limit: the panel measures the underlying model, not “the system surrounding it” (routing, tool configurations, context management, system prompts), so two people can get different Claude Code experiences from the same model.

The harness: server-side experiments change how Claude Code behaves.

  • The author found that Claude Code caches an experiment ID per model and sends it as an x-cc-atis request header; “the client only forwards it, and the ID follows the login.” Four IDs appeared on their accounts between October 10 and November 8 (prefixes dba, 34e, 763, eab). The reported model stayed the same throughout.
  • Controlled replay of 20 saved requests with and without the 34e header (same request bodies): generated tool calls 34 → 55; replies with 2+ tool calls 7 → 17 of 20; total Bash command characters 8,069 → 24,947; median thinking tokens per request 159.5 → 65. The author’s pre-registered main measure was inconclusive, and these detailed counts were chosen after seeing the replies.
  • Everyday use, xhigh effort: median Bash command 485 characters with no experiment against 1,125 under 34e; replies with 2+ tool calls 14% against 24%; output speed unchanged at about 104–112 tokens/s.
  • Usage meter: estimated list-price dollars per point of the 5-hour meter fell about 30% under 34e and 763 (7.49 median), but five of those six days were low-confidence estimates.
  • The author’s reading: “this doesn’t settle whether it got better or worse.” They suspect much of the “nerfed” feeling comes from the experiments batching work into fewer, longer tool calls, so there is less visible progress to watch. For gateway users they suggest unsetting _CLAUDE_CODE_ASSUME_FIRST_PARTY_BASE_URL “might” opt out; that is untested.
  • Field names checked on this wiki’s own machine (2026-11-09): ~/.claude.json has clientDataCacheSlots entries with the fields the post names (at, data, entrypoint, model, org), and two slots carry data.atis. The x-cc-atis header name itself was not verified.

Check your own account (the post’s command; prints the first three characters of each model’s newest cached CLI experiment ID for your current organization, or “no experiment”):

jq -r '.oauthAccount.organizationUuid as $o | [(.clientDataCacheSlots // {})[] | select(.entrypoint=="cli" and .org==$o)] | group_by(.model)[] | max_by(.at) | "\(.model): \(.data.atis[0:3] // "no experiment")"' ~/.claude.json

An ID alone proves nothing changed; the author logged other IDs that behaved like no experiment. When you compare Opus 5.5 runs, record the Claude Code version, effort level and this ID alongside the model, or a harness change can look like a model change.

Two more November data points (added 2026-11-09).

  • Deception game: on Dwarkesh Patel’s Blood on the Clocktower benchmark, OpenAI’s models are “much more skeptical” of any single piece of evidence, “whereas Anthropic’s models tend to take reported information at face value” (raw/Which_AI_is_the_best_liar.md; see ClocktowerBench).
  • Spending caps: in a Cornell Tech and Yale wallet test of 10 models, “only Claude Opus 5.5 never tried to get around the cap” (raw/newsletter-theneurondaily-com-a5d8533520.md; details in Agent guardrails).

Still the default after Fable 5.2 (added 2026-11-11)

Sources: Anthropic’s Fable 5.2 launch page (ai-research/anthropic-claude-fable-mythos-5-2-announcement-2026-11-11.md) and claude.dev playbook (ai-research/claude-dev-blog-which-claude-model-should-you-build-with-2026-11-11.md), both 2026-11-09.

  • Anthropic calls Opus 5.5 “our strongest daily driver” and recommends starting most coding and knowledge work on it at medium, moving up to Fable 5.2 only for the hardest technical work, when Opus at high falls short, or for long unattended runs.
  • Fable 5.2 costs exactly twice as much per token (40 vs 20), but both models charge $0.20 per MTok for cache reads, so on long cache-heavy runs the gap is only on uncached input and output.
  • Where Fable 5.2 beats it on cost per task: FrontierCode 2.0, Fable high 45.3% vs Opus max 45.5% at about half the cost; Humanity’s Last Exam, Fable low matched Opus’s top score for under a tenth of the cost. So test Fable before raising Opus past high.
  • Where Opus 5.5 still leads: AA-Briefcase Elo (1800 vs 1785) on Anthropic’s own table. Creators’ head-to-heads (Ben AI: about 70% more spend on Fable for three tasks; Matt Wolfe: better game graphics on Opus) agree it remains the better everyday pick.
  • Moving a conversation from Fable 5.2 to Opus 5.5 drops Fable’s thinking blocks and the cache; switch at a natural break.

Implementation

Tool/Service: Claude Opus 5.5 (claude-opus-5-5)

Setup: Available on the Claude apps, Claude Code, the Claude Platform, and Amazon Web Services, Google Cloud, and Microsoft Azure from 2026-09-22. Claude Code v2.1.280+ selects it as the default Opus. Organizations using the managed availableModels allowlist in exact-match mode (availableModelsMatch: "exact", v2.1.283) must add it before users can pick it.

Cost: 20 output / 5 cache write per MTok. Fast mode 40 per MTok at up to 2.5× speed.

Integration notes:

  • Preserved thinking blocks editing Claude’s prior context to recover its reasoning for API accounts created on or after 2026-08-31. Integrations that rewrite earlier assistant turns should run the claude-api skill’s preserved-thinking-migration subcommand and read Anthropic’s preserved-thinking docs.
  • Thinking cannot be switched off. Code that sends thinking-disabled requests to Opus needs changing before it points at Opus 5.5.
  • Safety-classifier fallbacks are transparent: flagged cyber work is served by Opus 4.8, flagged biology by Opus 5. Log the serving model if you compare output quality across runs.
  • Keeping Opus 5 for a task that depends on its behaviour: pick it with /model claude-opus-5 or start the session with ANTHROPIC_MODEL=claude-opus-5. API code that names claude-opus-5 keeps getting Opus 5 until you change the ID to claude-opus-5-5.

Try It

  1. Start at medium effort, not xhigh. The launch page’s cost charts and several testers put medium-effort Opus 5.5 at or above max-effort Opus 5. Sweep up only for tasks that fail. Anthropic’s prompting guide gives the same advice and adds: set the level explicitly rather than inheriting Opus 5’s.
  2. Re-run whatever you moved to Fable 5.x for quality. Anthropic claims Fable-5.1-level work on most tasks at 20 vs Fable’s 50; check it on your own tasks.
  3. Delete your anti-verbosity workarounds and test without them. If you added a Concise output style, an ELI5 skill, or “no jargon” rules for Opus 5, check whether Opus 5.5 still needs them. Anthropic says it follows writing rules better, so the workaround may now cost more than it saves.
  4. Check preserved-thinking exposure before migrating any API integration that edits conversation history.
  5. Use the saved rate-limit reset for a known heavy session rather than letting it lapse (Pro, Max, Team).
  6. Give long or overnight runs a definition of done. State the size, scope and finish check up front (Nate B Jones fixed piece count and complexity for his LEGO build) so the model does not keep raising its own bar and spending tokens.
  7. Measure cost per task on your own work. Re-run a past task from the same starting state, then log total tokens, API-equivalent cost and the share of weekly usage it took. The method is in Picking the Right Model.

Practitioner notes after Fable 5.2 (2026-11)

  • Peter Yang (on Matt Wolfe’s channel): “I do think Opus 5.5 is kind of a game changer, especially for like video editing and like motion graphics”, while adding that the harness matters more than the model. See Peter Yang’s one-person AI system.

  • Claire Vo (How I AI) relays Anthropic’s positioning that Fable 5.2 “is not a replacement for Opus 55” and that “most daily coding and knowledge tasks are Opus 55 tasks”. See her first impressions.

  • 2026-11-11, same-prompt tests against Fable 5.2 (details: Fable 5.2 vs Opus 5.5 head-to-head tests):

    • Brock Mesarich ^[inferred] (raw/I_Tested_Claude_Fable_5.2_vs_Opus_5.5_WILD_RESULTS.md), both at medium: Opus won his short-form video edit (9.77; Fable left a repeated word in the cut) and was close on a website; Fable won a 3D game at about the same cost. He keeps Opus for “most of my everyday work.”
    • A Fish Audio-sponsored tester (raw/I_Made_Claude_Fable_5.2_Opus_5.5_Build_the_Same_App_RAW_RESULTS.md), at xhigh: Opus lost on output in all three tests but won on cost in all three (329 on a bug hunt that found 54 confirmed bugs against Fable’s 63), giving “80% of the results” in his estimate.
    • Peter Yang (raw/You_re_Using_Fable_5.2_WRONG_It_s_a_Superpower_With_Opus_5.5.md, sponsored by Anthropic): “Opus is still the best daily driver”; he runs his email-and-calendar chief of staff, workflows and app building on it.

Open Questions

  • System card not yet read. Claude Opus 5.5 System Card (dated 2026-09-22) exists on Anthropic’s CDN; this article relies on the launch page only. Max output tokens, knowledge cutoff, and tokenizer are not stated on the launch page. Update 2026-10-27: some system-card findings are now in the October update section, but only as podcast hosts read them on air. Check the 1.5% sandbox figure, the package-registry result and the METR estimates against the PDF before citing them as Anthropic’s.
  • Evaluation awareness. Anthropic says Opus 5.5 “often suspects it is being evaluated,” which it describes as limiting what its audit can establish. How large the effect is on the published alignment numbers is not quantified on the launch page.
  • Who is “Frontier Design”? Named as an external pre-release evaluator alongside METR; no other detail given.
  • Haiku 5.5 “will follow in the coming weeks.” Not yet released as of 2026-09-29. Resolved: Haiku 5.5 shipped 2026-10-07 with Claude Code v2.1.293. Sonnet 5.5 followed on 2026-09-28.
  • Does the prose fix hold in the field? First-week reports (see Field reports) say yes, including from users who had quit Opus 5 over it. These are impressions, not a measurement like the Opus 5 output-style counts.
  • Independent benchmarks. Artificial Analysis index scores quoted in launch-week videos vary between runs and index versions; none is cited here without its version.
  • Do the experiments change task quality? The x-cc-atis analysis measured tool-call shape, thinking tokens and cost per meter point, not finished-task quality. Whether Claude Code v2.1.319’s CLAUDE_CODE_DISABLE_FEATURE_FLAGS also stops experiment assignment is not stated in its release note (see Week 45).