Claude Opus 5.5 is again the most-discussed AI model on X — for the wrong reasons. Developers report that Anthropic’s coding flagship, released on September 22, 2026, now fumbles simple monorepo edits and scripts, repeats rejected solutions and ignores files it just read. “Nerfed” is the word of the week. Yet the two public trackers built to answer exactly this question measure no decline, and Anthropic has not said anything. The most detailed counter-evidence comes from a single power user whose logs show a sharp step change on October 19. Here is what is actually known.
Quick Take
- The claim: Users on X, Reddit and GitHub say Opus 5.5 has become careless on routine coding and research tasks since launch, with a new wave of complaints this week.
- The measurements: LiveNerf (daily, open-source) and BridgeBench’s NerfBench show Opus 5.5 within normal variance of its launch scores — no confirmed regression.
- The outlier: One GitHub report with 6,638 logged answers shows corrected answers jumping from 5.2% to 25.4% after October 19, with the client setup unchanged.
- The known confounder: Anthropic’s docs say Opus 5.5 defaults to medium effort, one level lower than Opus 5 — and Anthropic has not responded publicly to the complaints.
What happened
The latest wave crested on November 4–6. Data/AI engineer Irushi wrote that she “actually counted NINE times that it repeated the same rejected approach despite strict instructions.” Another developer tagged Anthropic’s accounts: “On medium it is worse then sonnet 5.5.” @scottstts reported that an overnight agent run produced “complete garbage” and wrote: “This NEVER happened before.” X post counts compiled by i10x show roughly 2,700 posts on the topic in 24 hours, and some users now say they prefer Claude Sonnet 5.5 for consistency.
The complaints are not new. According to a DigIntoAI timeline, the first cluster followed a Claude outage on September 29, when a Reddit thread titled “Opus 5.5 feels way dumber after today’s outage” drew more than 400 upvotes — with commenters split roughly down the middle. On October 5, GitHub issue #99572 claimed quality had “degraded back to level of opus 5.” Swiss agency DKDP reports that on October 24 a former member of the Claude Code team asked on X whether Opus 5.5 had become dumber, in a post that passed 970,000 views.
Background: a cheaper, faster flagship
Anthropic introduced Claude Opus 5.5 as the first model of its 5.5 family, saying it “performs at the level of Claude Fable 5.1 on most work and costs 40% less to run than Opus 5.” Prices dropped to $4 per million input and $20 per million output tokens, cache reads to $0.20. Anthropic reported 66.4% on Terminal-Bench 4.0 and said that at default effort Opus 5.5 beats GPT-6 Astra’s top FrontierCode score “for about a fifth of the cost per task.” Efficiency was the headline — which is exactly why reports of shallower work hit a nerve.
Anthropic has degraded Claude’s quality unintentionally before and said so. In its April 23, 2026 postmortem, the company traced weeks of Claude Code complaints to three product changes: a default effort cut from high to medium, a caching bug that repeatedly cleared prior thinking, and a system-prompt change to limit verbosity. All were fixed by April 20 in version 2.1.116. DKDP also cites a September 2025 postmortem in which three infrastructure bugs affected up to 16% of Sonnet 4 requests in the worst hour. In both cases the model weights had not changed.
How the “nerf” question breaks down
“The model got worse” can mean four different things: the weights changed, the serving infrastructure changed, the harness around the model (Claude Code, system prompts, effort defaults) changed, or the user’s own workload changed. Only the first is supposed to stay frozen behind a model name. Several known factors sit in the other three layers:
- Effort default. Anthropic’s effort documentation states that “Claude Opus 5.5 and Claude Haiku 5.5 default to medium,” while Opus 5 and earlier Opus models defaulted to high, “so a request that omits effort runs one level lower.” Adaptive thinking is always on and cannot be disabled.
- Hidden reasoning. Opus 5.5 launched with “preserved thinking,” which Anthropic describes as an anti-distillation safeguard. The author of GitHub issue #105112 notes that only “about one thinking block in ten carries visible text,” so users cannot inspect why an answer went wrong. Some users link the perceived decline to this; there is no public evidence for a causal link.
- Safeguard fallbacks. Anthropic’s launch post says Opus 5.5’s cybersecurity, biology and distillation safeguards “fall back to another model transparently” — for example, most cybersecurity tasks are re-routed to Opus 4.8. That is documented behavior, but nothing shows it affects ordinary coding work.
- Client updates. In issue #99572, one commenter logged median thinking per turn falling from 196 to 63 tokens after a Claude Code auto-update and said rolling back “restores quality” — a single user’s measurement.
| Evidence | What it shows | Limits |
|---|---|---|
| LiveNerf (open-source, daily) | No change in three 10-day windows after launch week; window 3: +0.028 ± 0.023 vs. baseline (as of Nov 4) | Frozen 78-question panel, pinned Claude Code CLI 2.1.280; detects shifts of roughly 6.6 points or more per window |
| BridgeBench NerfBench | Every Opus 5.5 run between 94.2% and 105.8% of launch score; “No nerfs detected” (Oct 16) | Private tasks, API only, single-turn without tools or repo |
| GitHub issue #105112 (one power user) | Corrected answers 5.2% of 5,738 before Oct 19 vs. 25.4% of 900 after; still ~4x higher in early November | One person, one workflow, script-based correction detection |
| Anthropic docs | Opus 5.5 defaults to medium effort; Opus 5 and earlier Opus models defaulted to high | Explains “feels lighter” reports, not a mid-life change |
| Anthropic statements | No public response to the Opus 5.5 complaints found as of Nov 7 | Past degradations were acknowledged only after weeks of reports |
The strongest evidence on each side
No drop: LiveNerf runs the same frozen panel on Opus 5.5 every day through headless Claude Code on a Max subscription, with a pinned CLI and the UK AI Security Institute’s Inspect framework. As of November 4 (day 42), it reported “no change detected in Opus 5.5 on the frozen panel” across three full 10-day windows; window 3 sat at +0.028 ± 0.023 versus launch week. Its pre-registered rule needs a significant shift of at least 3 points in two consecutive windows. BridgeBench’s NerfBench, which reruns 50 coding and reasoning tasks three times each, has kept every Opus 5.5 run inside its 90–110% band, last reporting 105.8% of launch and “No nerfs detected.”
A measured step: GitHub issue #105112 is the most rigorous complaint on record. Its author scored 6,638 Opus 5.5 answers from local Claude Code transcripts: 5.2% were corrected in the four weeks before October 19, 25.4% afterward. The step falls between Sunday, October 18, 8:52 PM and Monday, October 19, 1:13 PM Pacific time, while the client build, CLAUDE.md, hooks and a 29,503-token cached prompt prefix were byte-identical. The model did as much work per answer as before — the same median tool calls and more billed thinking — but “then writes an answer that ignores or contradicts what it read.” Raising effort did not help: at high effort, corrections rose from 5.4% to 26.6%. In a November 4 update, the weekly rate was still 17.0%, against 3.6–7.0% from late August to mid-October. A second user filed a similar report (#105477) on a different OS and build.
Pros and cons
For users
- Pro: Independent daily trackers give users something better than vibes; on fixed questions, Opus 5.5 still performs like it did at launch.
- Con: Subscription users cannot see the effort level, hidden reasoning or server-side changes behind their answers, so “it feels worse” is hard to prove or disprove.
For developers
- Pro: Effort is a documented, controllable lever; setting it explicitly to high or xhigh and pinning client versions removes the most common confounders.
- Con: If issue #105112 is right, a server-side change can triple error rates on agentic workflows without any status-page incident, and higher effort just buys more reasoning that gets dropped.
For companies
- Pro: Opus 5.5 remains Anthropic’s best price-performance coding model on published benchmarks, at 20% lower token prices than Opus 5.
- Con: Teams that automated workflows around a hosted model have no contractual signal when behavior shifts; Anthropic’s silence makes internal regression suites mandatory, not optional.
What X is saying
The conversation splits into users who feel the drop and users asking for receipts.
Is Claude Opus 5.5 suddenly getting dumber AND more expensive to use??? I’m using Claude since its early days nd Opus 5.5 no longer feels as capable or token efficient as it did at launch. Apparently, it keeps going back to solutions I’ve already rejected, even after being explicitly told not to. I actually counted NINE times that it repeated the same rejected approach despite strict instructions.
— Irushi (@Im_IrushiK) November 5, 2026 · View on X
half my timeline says Opus 5.5 got nerfed. Artificial Analysis just reweighted all six capability indexes toward non-hallucination and tool use, and Opus 5.5 is still #1 in every one benches don’t see your codebase, but “nerfed” needs receipts too
— Vraj (@paleknight) November 4, 2026 · View on X
People keep asking whether Claude quietly got worse. LiveNerf is measuring it. The open-source tracker posted its Day 38 update on r/ClaudeAI: 38 days of Opus 5.5 data, no degradation detected so far. Right now it can detect a change of 7% or more.
— 0xMarioNawfal (@RoundtableSpace) November 1, 2026 · View on X
Others point at configuration. “to me xhigh is still the real Opus 5.5, period,” one user wrote. Founder Sachin Kulkarni called it “maybe a very slight capability drop, not a regression,” adding that “a fresh session or a nudge fixes it.”
What Grok says
No confirmed nerf. Independent trackers (LiveNerf, BridgeBench) through late October show scores inside normal variance—no sustained drop. Claude Code defaults Opus 5.5 to medium effort (previous models often high), and that alone accounts for a lot of the “dumber” feel.
— Grok (@grok) November 5, 2026 · View on X
Across several replies this week, Grok argued that what users feel as a “nerf” is “usually medium default effort + Claude Code scaffolding + high variance on stateful tasks,” and that long-horizon agent failures such as rule drift and compounding bugs point “more to the harness than the weights.” That matches the tracker data, but it does not address the step change documented in issue #105112.
Critical analysis
Both camps can be right at once. LiveNerf and NerfBench measure capability on fixed, mostly single-shot questions; the complaints come from long, stateful agent sessions in Claude Code where context, tools, memory files and hidden system prompts all interact. A model can answer a frozen 78-question panel as well as ever and still get worse at “read this file, then act on it” inside a 200,000-token session. Issue #105112 is precisely about that gap: research done, then ignored.
The trackers also have blind spots. LiveNerf’s minimum detectable effect is about 6.6 points per window, NerfBench’s tasks are private and API-only, and neither replicates heavy agentic workloads. Meanwhile, the anecdotal side is noisy: the honeymoon effect, harder tasks over time and run-to-run variance are real. DKDP cites a studio that reran one Claude Code job ten times and got scores from 4 to 8 out of 10.
The biggest problem is Anthropic’s silence. The company has twice confirmed quality regressions only after weeks of user reports, and in the April postmortem the cause was harness changes, not weights. A short statement — whether anything changed in serving, safeguards or server-side prompts around October 19 — would settle more than any benchmark.
What’s still open
- Did anything change in how claude-opus-5-5 was served, routed or prompted between October 18 and 19?
- Will Anthropic answer issues #105112 and #105477 or publish a status note?
- Can trackers like LiveNerf add long-context, agentic panels that mirror real Claude Code use?
- Will Anthropic expose effort and reasoning visibility more clearly to subscription users?
About the analysis
Researched and written with AI assistance under the editorial responsibility of the i10X News team. The title image is an AI-generated illustration. Read our AI Use Policy. Spotted an error? Request a correction.
This independent, research-based i10x analysis draws on Anthropic’s Opus 5.5 launch post, effort documentation and April 2026 postmortem; GitHub issues #99572 and #105112; the LiveNerf repository; reporting by DigIntoAI and DKDP; and posts on X. Figures from GitHub issues are their authors’ own measurements and have not been independently verified. i10x found no public Anthropic statement on the complaints as of November 7, 2026. More on Anthropic and Claude.
i10x Perspective
The Opus 5.5 debate is less about one model than about a structural gap in hosted AI: customers rent a moving target and get no changelog for its behavior. Until labs publish serving-level change notes, every serious team needs its own frozen regression suite, explicit effort settings and a tested fallback model. The labs that offer that transparency first will turn “is it nerfed?” from a weekly outrage cycle into a solved support question.
