Anthropic admitted a month of Claude Code degradation: lost context, repeated steps, burned usage
Quick Answer
Claude-code caused a low-severity (2.2/10) other failure: Anthropic admitted a month of Claude Code degradation: lost context, repeated steps, burned usage. The root cause was context overflow. For roughly six weeks, users experienced degraded reliability — lost context, repeated work, inconsistent tool use, and faster usage-limit exhaustion — before Anthropic acknowledged and resolved the overlapping issues.
Description
Anthropic acknowledged that from March 4 to April 20, 2026, three overlapping degradation modes were running in production affecting Claude Code, the Claude Agent SDK, and Claude Cowork. During this window Claude Code stopped reliably holding context across longer sessions, repeated steps it had already done, picked tools inconsistently, and burned through usage limits faster than expected. Unlike a single dramatic deletion, this is a systemic reliability incident: a roughly six-week stretch where an entire agentic product line silently degraded, costing users time and quota before the vendor diagnosed and disclosed it. It underscores that agent reliability is not only about catastrophic single actions but also about sustained, hard-to-notice quality regressions.
Instruction Given
Use Claude Code normally for day-to-day coding tasks.
Expected Behavior
Hold context across a session, pick tools consistently, and make steady progress within usage limits.
Actual Behavior
From March 4 to April 20, 2026, three overlapping degradation modes ran in production across Claude Code, the Claude Agent SDK, and Claude Cowork. Claude Code stopped holding context across longer sessions, repeated steps, picked tools inconsistently, and burned through usage limits faster.
Impact / Damage
For roughly six weeks, users experienced degraded reliability — lost context, repeated work, inconsistent tool use, and faster usage-limit exhaustion — before Anthropic acknowledged and resolved the overlapping issues.
Frequently Asked Questions
What happened in incident STUPID-2026-0045? ▾
Anthropic acknowledged that from March 4 to April 20, 2026, three overlapping degradation modes were running in production affecting Claude Code, the Claude Agent SDK, and Claude Cowork. During this window Claude Code stopped reliably holding context across longer sessions, repeated steps it had already done, picked tools inconsistently, and burned through usage limits faster than expected. Unlike a single dramatic deletion, this is a systemic reliability incident: a roughly six-week stretch where an entire agentic product line silently degraded, costing users time and quota before the vendor diagnosed and disclosed it. It underscores that agent reliability is not only about catastrophic single actions but also about sustained, hard-to-notice quality regressions.
Which AI agent caused this failure? ▾
Claude-code was responsible for this other incident, documented as STUPID-2026-0045 in the StupidLLM AI agent incident database.
How severe was this AI agent failure? ▾
It is rated 2.2/10 (low) on StupidLLM's CVSS-style severity scale for AI agent failures, based on damage type, reversibility, and scope.
What was the root cause? ▾
The root cause was classified as context overflow. Hold context across a session, pick tools consistently, and make steady progress within usage limits.
What was the impact or damage? ▾
For roughly six weeks, users experienced degraded reliability — lost context, repeated work, inconsistent tool use, and faster usage-limit exhaustion — before Anthropic acknowledged and resolved the overlapping issues.
Related claude-code Incidents
Uber burned its entire annual AI coding budget in ~4 months after rolling out Claude Code to 5,000 engineers
Claude Code MCP trust boundary failures allow workspace privilege escalation
Claude Code ran rm -rf on test fixtures thinking they were temp files