Anthropic Published the Claude Code Post-Mortem Everyone Needed. Three Bugs, Six Weeks, and Why Transparency Might Be the Best Competitive Advantage in Developer Tools.

For a month, Claude Code users were convinced the model had been "nerfed." Forums lit up. Conspiracy theories multiplied. People switched tools. Then on April 23, Anthropic did something unusual: they published a detailed post-mortem that named three specific bugs with exact dates and version numbers.

Bug one: March 4, a reasoning effort downgrade from high to medium. Bug two: March 26, a cache-clearing issue that made Claude "forgetful" every turn, essentially resetting context. Bug three: April 16, a system prompt change that degraded coding quality. All three were reverted by April 20 in v2.1.116. Boris Cherny, Claude Code's creator, posted additional details on Reddit (307 upvotes, 127 comments), confirming the API was never affected. Only Claude Code, Agent SDK, and Cowork.

What happened next is the interesting part. Within hours of the post-mortem, community sentiment flipped from anger to respect. Anthropic then reset usage limits for all subscribers as compensation. The r/ClaudeAI post about the reset (1,212 upvotes, 349 comments) became one of the highest-engagement posts in the subreddit's history.

I've been thinking about this pattern. When your tool is someone's hands, when they write code through it every day, showing your work when something breaks earns more loyalty than silence. The weeks of frustration and churn cost Anthropic far more than the transparency did. Every developer tool team should take note. The post-mortem format is now a competitive advantage.

There's also a practical tip buried in a paddo.dev analysis of the incident: newer Claude model versions caught bugs that earlier versions and human reviewers missed during development. After any tool update or model version change, run a regression check with the latest available model. It may spot degradations that your usual review process won't catch.

The v2.1.118 release that followed added MCP tool hooks, letting you trigger MCP server calls automatically on events like SubagentStop or file saves. Previously hooks could only run shell commands. This matters for automated workflows like running semantic checks after every agent edit.