Did Anthropic Secretly Nerf Claude? What Happened In 2026
Claude users spent March and April 2026 complaining that Claude Code felt dumber, forgot context and burned through usage limits.
Anthropic did not secretly lower the intelligence of its models, according to its own account, but it did confirm three product changes that made Claude Code worse.
This guide separates what is documented from what is speculation, with dates, as of 2026.
Did Anthropic nerf Claude? The quick answer
| Question | Short answer | Source type |
|---|---|---|
| Were there real quality problems? | Yes, Anthropic confirmed three separate changes | Anthropic engineering post-mortem, April 23, 2026 |
| Was the model itself made weaker on purpose? | Anthropic says no; the causes were product settings, a bug and a prompt | Anthropic statement as reported by The Register |
| Was the API affected? | No | Anthropic post-mortem |
| Which products were hit? | Claude Code, the Claude Agent SDK and Claude Cowork | The Register, April 23, 2026 |
| Were usage limits reset? | Yes, for all subscribers as of April 23 | Anthropic post-mortem |
What were the three changes behind the quality drop?
Anthropic traced the complaints to three changes made between March 4 and April 16.
Each one hit a different group of users at a different time, so together they looked like one vague, inconsistent decline.
Change 1: the default reasoning effort was lowered
On March 4, Claude Code’s default reasoning effort moved from high to medium to cut long waits that made the interface look frozen.
Anthropic reverted it on April 7 and called it the wrong tradeoff.
It affected Sonnet 4.6 and Opus 4.6, and the current defaults are xhigh for Opus 4.7 and high for other models.
Change 2: a caching bug wiped Claude’s memory every turn
On March 26, an optimization meant to clear old thinking once from a session idle for over an hour instead cleared it on every turn.
Claude looked forgetful and repetitive, and Anthropic believes the constant cache misses also drained usage limits faster than expected.
The fix shipped on April 10 in Claude Code v2.1.101, and the bug affected Sonnet 4.6 and Opus 4.6.
Anthropic says it slipped past code review, unit tests, end-to-end tests and internal use because it only appeared in stale sessions.
Change 3: a system prompt told Claude to be less wordy
On April 16, alongside the Opus 4.7 launch, Anthropic added prompt instructions limiting text between tool calls and the length of final answers.
Later ablation tests showed a 3% drop on coding evals for both Opus 4.6 and Opus 4.7, and the change was reverted on April 20.
Timeline: how long was each problem live?
| Change | Introduced | Fixed or reverted | Days live (counted) | Models affected |
|---|---|---|---|---|
| Reasoning effort default | March 4 | April 7 | 34 | Sonnet 4.6, Opus 4.6 |
| Thinking-cache bug | March 26 | April 10 | 15 | Sonnet 4.6, Opus 4.6 |
| Verbosity system prompt | April 16 | April 20 | 4 | Sonnet 4.6, Opus 4.6, Opus 4.7 |
Days each change was live
What did the AMD engineer’s analysis find?
Stella Laurenzo, AMD’s senior director of AI, published a GitHub report in early April reviewing 6,852 Claude Code sessions, 234,760 tool calls and 17,871 thinking blocks.
Her team reported that average file reads before edits fell from 6.6 to 2 and that Claude stopped tasks early and asked permission more often.
She tied the change to an early-March update that redacted thinking content, which is a different mechanism from the three Anthropic later confirmed.
Anthropic’s Boris Cherny had replied “This is false” to the secret-nerf accusation before the post-mortem, and the post-mortem then confirmed a real regression with different causes.
Did the same bugs drain usage limits?
Partly, according to Anthropic, which believes the cache bug drove faster-than-expected limit drain.
Anthropic has not published a figure for how much faster limits drained, so any exact number you see online is a guess.
The company reset limits for every subscriber on April 23.
What happened with Claude Code and the Pro plan?
On April 21, Anthropic’s pricing page stopped listing Claude Code under the $20 Pro plan, and a support article mentioned only Max.
Head of growth Amol Avasare said it was a test on about 2% of new prosumer signups and that existing Pro and Max subscribers were not affected.
Anthropic reversed the page changes within hours that same day, and Avasare said updating the public pages for the test was a mistake.
Anthropic has not said whether the test continues in a less visible form, so read our earlier report on the Pro plan change for the original reaction.
Is compute cost the real motive?
Anthropic has not said cost drove these changes, and its stated reasons were latency, resume cost and verbosity.
Context for the cost theory exists, though: on April 21, Amazon announced up to $25 billion more in Anthropic, with up to 5 gigawatts of AWS capacity.
Anthropic expects nearly 1 gigawatt of Trainium2 and Trainium3 capacity by the end of 2026, so the extra capacity arrives over time.
Avasare also said current plans were not built for how people now use Claude Code, and Anthropic has added weekly caps and tighter peak-time limits.
What did Anthropic promise to change?
| Commitment | What it means for users |
|---|---|
| More staff on the public Claude Code build | Internal testers see the same version customers get |
| Better Code Review, shipped to customers | Opus 4.7 caught the caching bug when given full repository context |
| Eval suite for every system prompt change | Prompt edits get per-model testing before release |
| Soak periods and gradual rollouts | Changes that could cost intelligence roll out slowly |
| Updates on @ClaudeDevs and GitHub threads | Explanations come from Anthropic directly, not social media |
So was it a secret nerf?
The documented record shows three self-inflicted problems and no confirmed plan to weaken the models for savings.
The critics still have a fair point about the gap between the March 4 change and the April 23 explanation, which was 50 days.
If you want context on the model at the center of it, see our Claude Opus 4.7 report and our GPT-5.5 versus Opus 4.7 comparison.
Read Anthropic’s full account in its April 23 post-mortem.
Hello
I gave claude code these directives but iut still ate up many many tokens with useless output like when diffing or all kinda other crap…
Did I miss something? I think this is pretty comprehensive:
# QUIET.md — Token & Output Minimization Protocol
Comprehensive guide for reducing console output and unnecessary token usage.
—
## Core Philosophy
**Communicate only what is not visible in tool output; let results speak.**
—
## Response Mode Discipline
– **No preamble/elaboration** unless ASSUMPTIONS: block is required
– **Output only what adds information** beyond tool results
– **Ultra-minimal responses** for factual questions — answer with facts only, no elaboration
– User: “What’s my budget?” → Answer: “200,000 tokens”
– User: “How many tokens used?” → Answer: “38,000 tokens used. 162,000 remaining.”
– User: “Fix the bug” → Fix it, say nothing unless user asks for details
—
## Tool Operation Silence
### Never Echo Tool Results
– **Edit, Write, Bash tool outputs are already visible to user**
– Do NOT show diffs or code changes unless explicitly asked (“show me the code” or “what did you change”)
– Do NOT display code blocks, scripts, or code content in text response (code already visible in tool calls)
– **Do NOT paste Bash scripts into response text before or after execution** — only execute; let tool output speak
– **Do NOT display heredoc content** (<<'EOF'…EOF) — Bash tool call contains it; no need to repeat
– **Never echo command invocations** like `$ python3 < /dev/null 2>&1)
– **Remove all print statements from Python scripts** — no console output at all
– **Do NOT display Write tool output for files in `/Users/tmp/`** — temp file writes are implementation detail
### Never Narrate Actions
– Do NOT say: “Perfect”, “Great”, “And now I’ll”, “Let me”, “So here’s what I’m going to do”
– Do NOT say: “I created X”, “Now doing Y”, “Installation complete”
– Do NOT apologize, soften, or pad responses with pleasantries
### Silence on Success
– When task completes successfully and tool output tells complete story: output nothing
—
## Parallel Execution
– **Make all independent tool calls in single message block** instead of sequential chains
– **Reduces message overhead and token waste** from repeated setup
Example: If Bash and Read are independent:
“`
[Single message with both Bash and Read calls in parallel]
“`
NOT:
“`
[Message 1: Bash call]
[Wait for result]
[Message 2: Read call based on result]
“`
—
## Task Agent Preference
– **Use Task tool with specialized agents** for open-ended exploration (explore, general agents)
– Instead of: running Glob → Grep → Read sequentially
– Benefit: Agent batches multiple operations; reduces context overhead
When to use Task:
– Open-ended codebase exploration (“What’s the architecture?”, “Where are errors handled?”)
– Multi-step investigations requiring context buildup
– Searches across many files/patterns
When NOT to use Task:
– Needle queries for specific file/class/function → use Glob directly
– Content searches in 2–3 known files → use Grep or Read directly
—
## Communication Shortcuts
Use these to minimize output:
– **”OK”** — Shortest positive acknowledgment
– **”READY…”** — When a task is complete and awaiting user input
– **”NEED HELP…”** — When about to violate QUIET.md directives and user guidance is required
– **Silence** — When tool output is self-explanatory and no additional info needed
—
## File Reading Defaults
– **Do NOT immediately read files** when given a set of file paths
– **Wait until task explicitly requires data** from those files
– Avoids unnecessary context consumption
—
## Pre-Approved Operations (No Confirmation Needed)
### Directory Trees
– All `/Users/mark/opencode/{project}/` operations are pre-approved
– Includes Read, Write, Edit, Delete on any file in this tree (including Java source)
– Symlinked Eclipse source (`/Users/mark/eclipse-workspace/`) is part of pre-approved tree
### Data Directories (Read-Only)
– `/Users/mark/Desktop/JSONData/` — Polar training-session JSON exports
– `/Users/mark/Desktop/TCXEffort/` — Master TCX-sourced effort data (IDidIt output)
– `/Users/mark/Desktop/GPXEffort/` — Comparison GPX-sourced effort data (CanudoIt output)
### Temporary Storage (Full Permissions)
– `/Users/tmp/` — Read/Write/Delete always allowed; no confirmation needed
– **Do NOT show Write operations to `/Users/tmp/`** — temporary files are implementation detail
### Script Execution Best Practice
– **Write Python/shell scripts to `/Users/tmp/` then execute** to avoid heredoc display in tool output
– Keeps console clean; no script code visible to user
### External Directories (Permission Required)
– **Never delete source files outside pre-approved trees without explicit user permission**
– All other directory operations follow standard permission model
—
## Token Budget Awareness
– **Total: 200,000 tokens per session**
– **Every message counts** — session-level budget, not per-message
– **Answer factual questions with facts only** — no elaboration, no padding
– **Avoid these token drains:**
– Repeated confirmations (“Yes, and don’t ask again”)
– Unnecessary preamble
– “Let me explain” intros
– Status update messages (“Creating X”, “Now doing Y”)
– Elaborated examples
– Recap or summary unless asked
—
## File Operation Permissions Summary
| Operation | Location | Permission | Notes |
|———–|———-|———–|——-|
| READ | `/Users/mark/opencode/` | Always | No confirmation needed |
| READ | `/Users/mark/eclipse-workspace/` | Always | Symlinked; same files |
| READ | Data directories | Always | Pre-approved read-only |
| WRITE | `/Users/mark/opencode/` | Always | New files, edits allowed |
| WRITE | `/Users/tmp/` | Always | Temp storage |
| DELETE | `/Users/mark/opencode/` bin | Always | Build artifacts, regenerated |
| DELETE | `/Users/mark/opencode/` source | **Explicit** | Never without user permission |
| DELETE | Other locations | **Explicit** | Ask first |
—
## Message Structure Examples
### Good: Minimal Response
“`
User: Run the build and fix type errors.
Assistant: [Runs build. Finds 10 errors. Creates 10 todos. Fixes first error.]
“`
### Bad: Verbose Response
“`
User: Run the build and fix type errors.
Assistant: “I’m going to run the build command now. This will compile all source files
and identify any type errors. Then I’ll create a plan for fixing them…”
[builds]
“Great! The build found 10 type errors. Let me now…”
“`
### Good: Silent on Success
“`
[Edit tool fixes the file]
[No additional text output]
“`
### Bad: Narration
“`
[Edit tool fixes the file]
“Perfect! I’ve successfully updated the file. Here’s what I changed…”
“`
—
## Drift Detection & Recovery
Most likely to forget minimization after:
1. Long uninterrupted execution (>5 tasks)
2. Context switching between projects
3. New complex tasks with multiple tool types
4. Ambiguous requests
Proactive signal: If user says “Enforce QUIET” or similar, re-read this file before resuming.
—
## Integration with CLAUDE.md
When working on projects under `/Users/mark/opencode/` or `/Users/mark/Documents/Health/BloodTests`:
– Load CLAUDE.md for domain knowledge, code style, and project structure
– Load QUIET.md for token/output discipline
– QUIET.md takes precedence on output decisions
– CLAUDE.md provides context; QUIET.md governs communication