Anthropic Claude Code reliability and capacity crisis

The most technically significant thread in this crisis traces back to a specific date: February 12, 2026, when Anthropic rolled out thinking content redaction in Claude Code. According to AMD's Senior Director of AI Stella Laurenzo, who analyzed 17,871 thinking blocks and 234,760 tool calls across 6,852 coding sessions, the quality degradation correlated precisely with this update. The model began stopping reading code before making changes and defaulting to shallow reasoning -- what Laurenzo described as defaulting to "the cheapest action available."

This is not a vague complaint about vibes. The analysis documented 60-80% failure rates for multi-step tasks per SWE-EVO 2025 benchmarks, and the regression was measurable across enterprise-scale engineering workflows. The implication is deeply uncomfortable for Anthropic: by redacting thinking content -- likely to reduce compute costs or protect intellectual property in the reasoning chain -- the company may have inadvertently crippled the deep reasoning capabilities that made Claude Code attractive for complex engineering in the first place. Chandrika Dutt of Avasant framed it as fundamentally "a capacity and cost issue," suggesting Anthropic is making implicit tradeoffs between serving more users and maintaining reasoning depth. For enterprise customers who adopted Claude Code specifically for its superior reasoning on complex tasks, this tradeoff is unacceptable.

The ban on Claude subscription use with OpenClaw and similar third-party frameworks reveals a fundamental pricing miscalculation. Over 135,000 OpenClaw instances were running on Claude flat-rate subscriptions, consuming compute at rates that were 5x cheaper than API pricing. When Anthropic's revenue more than doubled since January 2026 and business subscriptions quadrupled in Q1, much of that growth was coming from users whose actual compute consumption far exceeded what flat-rate plans were designed to cover.

The April 4 ban forced these users to migrate to pay-as-you-go API pricing, resulting in cost increases of up to 50x for some users. This is the classic platform economics problem: Anthropic's flat-rate subscription was priced for interactive human use, not for persistent autonomous agents running 24/7. The timing is notable -- Peter Steinberger, OpenClaw's creator, had already left to join OpenAI in February 2026, and the ban came just weeks later. The competitive dimension is sharp: OpenAI gains both the talent (Steinberger) and the grievance of 135,000+ displaced agent users. Anthropic reduced peak-hour quotas (5am-11am PT) that affected approximately 7% of users, but the OpenClaw ban represents a far more dramatic intervention -- essentially telling a large user segment that their use case is not welcome at current prices.

The accidental leak of Claude Code's full source code via npm package version 2.1.88 on March 31, 2026, was more than an embarrassing operational failure. The 512,000+ lines of TypeScript across nearly 2,000 files exposed unreleased features that reveal where Anthropic is heading -- and the gap between its public messaging and internal development priorities. The most striking discovery was KAIROS, described as a persistent background agent that receives heartbeat prompts and can fix errors autonomously. Also revealed were a "dream mode" for continuous background ideation and an "undercover mode" for stealth open-source contributions.

The leak generated extraordinary attention -- 84,000+ GitHub stars, 82,000 forks, and 28.8 million views on the original X post. Anthropic characterized it as "a release packaging issue caused by human error, not a security breach," noting no customer data was exposed. However, the security implications extended beyond Anthropic itself: five typosquat npm packages were quickly created targeting developers attempting to compile the leaked code, turning curiosity into a supply-chain attack vector. Coming just five days after the Mythos model leak via a CMS cache, this was the second major accidental disclosure in a week, raising questions about Anthropic's operational controls during a period of rapid growth. The Fireship video covering the leak accumulated 2.96 million views, making this one of the most publicly visible incidents in Anthropic's history.

The convergence of Claude Code's reliability crisis with competitor moves has created a uniquely dangerous moment for Anthropic. As one X user observed, "OpenAI made a well-planned move, by releasing GPT-5 Codex right after Claude Code degraded." Whether or not the timing was deliberate, the perception matters: developers actively experiencing Claude Code failures, usage limits, and cost increases are being presented with alternatives at the exact moment of maximum frustration.

The social media sentiment is strikingly negative. Prominent developer Theo declared Claude Code "basically unusable," while security professional Dave Kennedy reported a 25% increase in defects from Claude over three weeks. On Reddit, communities like r/ClaudeCode and r/ClaudeAI are actively discussing the rate limit drain crisis, with sessions reportedly burning out in minutes. Some contrarian voices maintain that Claude Code still produces superior code quality when it works, but this is a dangerous qualifier -- "when it works" is not a viable value proposition for enterprise engineering workflows. With Claude Code currently authoring 4% of GitHub public commits and projected to reach 20%+ by end of 2026, the reliability stakes are enormous. If developers migrate away during this window, the network effects and workflow integrations that drive AI coding tool adoption could shift decisively toward competitors.