Developer Shane Melaugh alleged on November 7, 2026, that Claude Opus 5.5 had been “nerfed” after an analysis of 1,400 Claude Code sessions found an abrupt change in its displayed thinking around November 3. His post attracted more than 500,000 views in the captured X page, while a linked Hacker News discussion drew hundreds of points and comments.
The visible change has supporting evidence. A capability downgrade remains unconfirmed. Theo Browne’s separate analysis of 458,000 Opus 5.5 responses found a similar shift in summary wording, arriving at different times across accounts, without the deterioration he expected to see in several operational metrics. Anthropic’s documentation supplies a crucial explanation: the displayed thinking is a summary produced by a different model.
For Claude Code users, that distinction matters. A change in how Claude describes its work can look like a change in how it reasons. The available evidence supports investigating the presentation layer first, while leaving complaints about answer quality open.
Anthropic had not publicly confirmed either a summarizer rollout or a model downgrade in the reporting reviewed here. LLMs Blog reported no public company comment as of early November 9.
What Melaugh’s 1,400 Sessions Show
Melaugh said he used Gemini 4 Argon to analyze his Claude Code sessions. The resulting chart tracked wording patterns in visible thinking blocks from October 9 through November 7, with a sharp transition around 18:00 UTC on November 3.
According to the chart details reported by LLMs Blog, blocks beginning with “I’m” rose to 61.3%. Blocks containing expressions about what the model should or needed to do fell to 10.9%, while blocks containing dashes fell to 6.5%. The chart identified the model ID and CLI version as unchanged.
Those are useful observations about text. They show a change in the material users were reading, with a reasonably specific time attached.
The chart also included an important qualification:
“Visible summaries show a behavior shift, not proof of changed model weights.”
Melaugh’s broader allegation went further. In follow-up posts, he described a bug-fixing task where Opus 5.5 at high effort struggled for three hours, while xhigh found a fix within minutes. He later clarified that his investigation began with personal frustration and was not a scientifically rigorous benchmark. Those are his reported experiences, not results reproduced by this publication.
My view is that the chart is more useful than the downgrade label. It identifies a specific behavior that another observer could investigate. The bug-fixing example raises a separate question about task performance, but one comparison cannot isolate whether effort settings, context, randomness or a service change caused the difference.
Browne Found the Style Shift Across Multiple Accounts
Theo Browne’s analysis covered 458,000 Opus 5.5 responses from October 9 through November 7. His traffic showed the same broad wording transition, but accounts switched at different times between October 30 and November 4. One switched at approximately 18:00 UTC on November 3, matching the time in Melaugh’s chart.
Sysnote’s account of Browne’s analysis says the traffic used Claude Code 2.1.280 with thinking display set to summarized. Browne interpreted the staggered transitions as evidence of an account-by-account reasoning-summarizer rollout.
His reported before-and-after figures separate the visible style change from several measures of model activity:
| Measure | Before the switch | After the switch |
|---|---|---|
| Summaries beginning with “I’m” | 27% | 61% |
| Median summary length | 325 characters | 440 characters |
| Reasoning tokens per response | 369 | 413 |
| Reasoning share of output tokens | 46% | 49% |
| Output speed | 111 tokens/second | 112 tokens/second |
| Tool calls per response | 1.03 | 1.06 |
Figures reported in LLMs Blog’s coverage of Browne’s analysis.
The summary wording changed substantially, and the median summary became longer. Reported reasoning-token use increased, while speed and tool-call frequency stayed close to their earlier values. Browne said he found no sign of degraded capability in his traffic.
Two qualifications matter. Melaugh’s sessions and Browne’s responses are different units, so the sample sizes are not interchangeable counts of equivalent trials. Both analyses also used private datasets that were not published for independent verification or audit.
More importantly, the table is not a coding-accuracy benchmark. A response can use the same number of tools, arrive at the same speed and still produce a worse patch. These measurements weaken the specific idea that the wording shift necessarily reflects less reasoning, but they cannot settle every quality complaint.
The staggered timing strengthens the summarizer explanation because it resembles a gradual service rollout. It still cannot identify, by itself, which server-side component changed.
Anthropic Documents a Separate Thinking Summarizer
Anthropic’s thinking documentation explains that the visible text in a thinking block is a summary, not the model’s raw chain of thought. It states:
“Summarization is processed by a different model from the one you target in your requests”
That creates two distinct components to consider:
- Opus 5.5 performs the underlying reasoning and produces the response.
- A separate model turns that reasoning into the summary users can read.
Anthropic also documents that summarization behavior is subject to change and that the thinking model does not receive the summarized output. A change in the summarizer’s phrasing can therefore happen independently of a change to Opus 5.5.
This is the consequential detail behind the controversy. Counting first-person sentence openings measures the output of the summarization layer. It is not a direct measurement of Opus’s internal reasoning style, model weights or problem-solving accuracy.
The billing rules reinforce that separation. Anthropic says users are charged for the full thinking tokens, not the shortened summary text. The number of visible characters is consequently a poor proxy for how much reasoning was performed. A shorter display could summarize the same underlying work more aggressively; a longer display could simply be more verbose.
Hidden Thinking Is a Display Setting
The Opus 5.5 migration guide says the model defaults to medium effort and omits thinking text by default on the API unless summarized thinking is requested.
The thinking configuration’s display field controls this distinction:
summarizedreturns the readable summary.omittedreturns thinking blocks with an empty thinking field.
Omitting the text does not mean reasoning is disabled, and it does not remove the associated thinking-token charges. Display and reasoning are separate controls.
Those are API defaults, not evidence that a particular Claude Code session silently changed effort. Users investigating a regression should record their actual configuration instead of assuming the visible summary reveals it.
Quality Complaints Remain a Separate Question
Frequently Asked Questions
3 questions
1Is Claude Opus 5.5 Confirmed to Be Nerfed?
No. The documented wording shift is not proof of reduced capability. Browne’s traffic analysis supports a summarizer-change explanation, but neither private dataset settles every quality complaint.
