Claude Code Performance Regression Diagnosed: Configuration, Not Model Intelligence

Anthropic published a postmortem on Claude Code's recent performance regression. The finding runs counter to initial community framing: the degradation was not the model getting dumber. It was three product configuration changes.

Three Specific Changes That Caused the Regression

• Default reasoning effort downgrade: The harness reduced the default reasoning effort, leading to shallower analysis.
• Session caching bug: A bug wiped prior thinking from the cache, breaking continuity across turns.
• Prompt-verbosity change: A prompt modification reduced verbosity, lowering code output quality.

Anthropic rolled back these changes in the latest patch, and performance returned to previous levels — same model, different configuration, different behavior.

Implication for Teams Using AI Coding Agents

The practical takeaway is about the unit of trust. If you trust the model, you switch models when behavior changes. If you trust the instance, you look for evidence that configuration shifted. These two responses require completely different tooling — most teams lack session-level evidence and rely on gut feelings about which agent is performing.

The postmortem is useful not because it resolves the debate but because it demonstrates what an evidence layer looks like when you actually have one. For teams running Claude Code, tracking session-level configuration deltas and cache state is now a practical necessity.