Back to list
Anthropic Addresses Claude Code Quality Degradation Reports and Implements Fixes for Sonnet and Opus Models
Industry NewsAnthropicClaudeAI Engineering

Anthropic Addresses Claude Code Quality Degradation Reports and Implements Fixes for Sonnet and Opus Models

Anthropic has released a postmortem addressing recent user reports regarding the degradation of Claude's performance across specific tools, including Claude Code, the Claude Agent SDK, and Claude Cowork. The investigation identified three distinct technical issues occurring between March and April 2026: an intentional but poorly received reduction in reasoning effort to manage latency, a session-clearing bug that caused repetitive behavior and memory loss, and a system prompt change aimed at reducing verbosity that inadvertently harmed coding quality. While the API remained unaffected, these issues impacted Sonnet 4.6, Opus 4.6, and Opus 4.7. Anthropic has since reverted the problematic changes and fixed the bugs as of April 20 (v2.1.116), emphasizing their commitment to maintaining model intelligence over speed.

Hacker News

Key Takeaways

  • Three Distinct Issues Identified: The perceived degradation was caused by a change in reasoning effort, a session-clearing bug, and a system prompt instruction to reduce verbosity.
  • Specific Tools Affected: Issues were limited to Claude Code, the Claude Agent SDK, and Claude Cowork; the core API and inference layer were not impacted.
  • Models Impacted: The performance dips affected Sonnet 4.6, Opus 4.6, and Opus 4.7 across different timeframes.
  • Full Resolution: All identified issues were resolved as of April 20 with the release of version 2.1.116.

In-Depth Analysis

Reasoning Effort and Latency Trade-offs

On March 4, Anthropic attempted to address UI latency issues where the interface appeared frozen by changing the default reasoning effort from "high" to "medium." While this was intended to improve the user experience by reducing wait times, it resulted in a noticeable drop in intelligence for Sonnet 4.6 and Opus 4.6. Following user feedback indicating a preference for higher intelligence over speed, Anthropic reverted this change on April 7. The company acknowledged that prioritizing lower latency at the expense of reasoning quality was the "wrong tradeoff."

Technical Bugs and Prompting Side Effects

Two additional technical factors contributed to the degradation. On March 26, a feature designed to clear old thinking from idle sessions to improve resumption speed introduced a bug. This bug caused the system to clear thinking every turn, making the models appear forgetful and repetitive. Furthermore, an April 16 update to the system prompt intended to reduce verbosity negatively impacted coding quality when combined with other prompt adjustments. This specific issue affected the latest models, including Opus 4.7. Both the bug and the prompt changes were corrected and reverted by April 20.

Investigation Challenges and Aggregate Effects

Anthropic noted that because these three changes occurred on different schedules and affected different segments of traffic, the resulting feedback appeared as broad and inconsistent degradation. The investigation began in early March but was complicated by the difficulty of distinguishing these specific technical failures from the normal variation in user feedback. The company has reaffirmed that they never intentionally degrade models and are implementing changes to prevent similar regressions in the future.

Industry Impact

This incident highlights the delicate balance AI providers must maintain between model "intelligence" (reasoning effort) and operational performance (latency). For the AI industry, it serves as a case study in how minor optimizations—such as reducing verbosity or clearing session cache—can have significant, unintended consequences on the quality of complex tasks like coding. Anthropic's transparent postmortem underscores the importance of user feedback loops in identifying non-obvious regressions that automated testing might miss, particularly when those regressions are tied to UI-specific implementations rather than the underlying API.

Frequently Asked Questions

Question: Was the Claude API affected by these quality issues?

No. Anthropic confirmed that the API and inference layer remained unaffected throughout this period; the issues were isolated to Claude Code, the Claude Agent SDK, and Claude Cowork.

Question: Which Claude models were impacted by the performance degradation?

The issues affected Sonnet 4.6, Opus 4.6, and Opus 4.7, depending on the specific technical change and the timeframe.

Question: How has Anthropic resolved these issues?

As of April 20 (v2.1.116), Anthropic has reverted the reasoning effort to "high," fixed the session-clearing bug, and removed the system prompt instructions that were harming coding quality.

Related News

How Google Duplex Evolved to Call Businesses on Your Behalf in Gemini
Industry News

How Google Duplex Evolved to Call Businesses on Your Behalf in Gemini

A Google Research Blog entry titled “How Google Duplex evolved to also call businesses for you in Gemini” describes its subject as the evolution of Google Duplex to support calls to businesses on a user’s behalf in Gemini. The entry is dated November 20, 2026, and the supplied article text consists only of the label “Generative AI.” The headline identifies the capability and connects it to Duplex, but the available text does not explain how the system evolved, how users request a call, or where the feature is available. The headline establishes the topic, but the supplied material does not provide a technical account or rollout details.

How AI and Lean Are Helping Automate Formal Verification to Fight Software Slop
Industry News

How AI and Lean Are Helping Automate Formal Verification to Fight Software Slop

In Latent Space, Richard MacManus examines formal verification as an emerging way to fight what the headline calls “slop.” The central claim is that proving software correct with mathematics has traditionally required specialist work, and that AI and Lean are now helping automate that process. The distinction is important: the reported change concerns how the work of proving correctness is done, not what counts as a proof. The supplied excerpt presents automation as assistance, without saying that it replaces specialists or completes proofs independently. It also does not specify which parts of the process AI and Lean help automate, how much work they save, or which software has been verified this way.

AI and Human Claim Solutions to the 167-Year-Old Riemann Hypothesis
Industry News

AI and Human Claim Solutions to the 167-Year-Old Riemann Hypothesis

TechCrunch AI reports that AI claimed a solution to the Riemann hypothesis, a mathematical problem the headline describes as 167 years old. A human also put forward a competing solution. The report, written by Tim Fernholz and published on November 20, 2026, describes mathematicians as astonished by the AI-driven result. The supplied excerpt does not explain either proposed solution, identify the AI system or the human claimant, or say whether either claim has been verified. The distinction between a claimed solution and a confirmed one is central to reading the report: the excerpt establishes that two claims are being reported, but it does not establish that either has resolved the hypothesis.