I reverse-engineered why Claude Code burns through your usage so fast. 7 bugs that stack on top of each other — and the worst one activates when Extra Usage kicks in | AI Paper Digest

TL;DR Highlight

A Max 20x subscriber reverse-engineered the Claude Code CLI source and discovered 7 bugs that drain usage abnormally fast. The core issue is a 'death spiral' where switching to Extra Usage demotes cache TTL from 1 hour to 5 minutes, causing costs to spike 2.8x.

Who Should Read

Developers using Claude Code CLI, especially Max plan or Extra Usage subscribers. Essential reading for anyone who has noticed their usage draining faster than usual.

Core Mechanics

Most severe bug: an internal function in cli.js detects Extra Usage status and automatically demotes the cache TTL requested from the server from 1 hour to 5 minutes. Taking a break longer than 5 minutes raises the per-turn cost from $0.22 to $0.61 (2.8x) on a 220K context.
This demotion happens client-side only. The server accepts 1-hour TTL requests normally, and patching the function in cli.js to always return true causes the server to grant 1 hour.
The 'death spiral' structure: other bugs rapidly exhaust plan usage → Extra Usage activates → cache demoted to 5 minutes → one bathroom break triggers a full rebuild → Extra Usage drains instantly → locked out until the 5-hour reset.
The native installer binary includes a custom Bun runtime that corrupts the cache prefix on every request. Installing via `npm install` resolves this; `file $(which claude)` should return a symlink, not an ELF binary.
Between v2.1.69 and v2.1.90 (28 days, 20 versions), certain attachment types were missing on session resume, causing a cache miss every time. Fixed in v2.1.91.
The Autocompact feature had no circuit breaker, causing failed compactions to retry infinitely. Internal source comments recorded 50+ consecutive failures across 1,279 sessions. Fixed in v2.1.89.
The client generates fake rate limit errors without making actual API calls when transcripts grow long. Responses show `model: synthetic` with 0 tokens. Not yet fixed.
Server-side compaction silently removes tool results mid-session, breaking the cache. Cannot be patched client-side. Not yet fixed.

Evidence

A Max 20x user on WSL noticed usage draining noticeably faster recently; switching from the native install to the npm version brought drain speed back to normal, and they shared this experience directly.
As a counterpoint, some heavy Max plan users claimed their usage had not changed at all compared to months ago and asked why it wasn't happening to everyone. The OP explained that bugs 1+3+5 must all occur simultaneously for the worst case of exhausting a weekly quota within 2 hours.
One user had tried the native installer when it first launched, ran into issues, and switched back to the npm version — and had not experienced any of the recent issues since, as shared in the comments.
A link to a cache analysis tool was shared in the comments: `https://github.com/abhiyan-maitri/claude-usage-report` — allows you to check cache usage per prompt.
There was significant criticism that the post was written with Claude. Alongside cynical remarks that 'this sub has become a place where bots post for bots,' criticism also emerged that the Claude Code team no longer carefully reviews Claude-generated code, which is why these bugs went unaddressed for 20 releases.
Some took a charitable view, noting that Anthropic is already subsidizing costs as much as possible, so fixing these bugs would benefit Anthropic as well.

How to Apply

If you installed Claude Code via the native installer, reinstall with npm right now. If `file $(which claude)` returns an ELF binary, you have the native version. Switch with `npm install -g @anthropic-ai/claude-code` to resolve the cache prefix corruption bug (#1).
If you are on a version below v2.1.91, update immediately. The session-resume cache miss bug (#2) and the Autocompact infinite loop bug (#3) were fixed in v2.1.91 and v2.1.89 respectively.
If you are concerned about cost spikes from Extra Usage, you can patch the cache TTL decision function in cli.js to always return the 1-hour value. Note that updates will overwrite the patch, so you will need to reapply it after each update. Technical details are in GitHub issue anthropics/claude-code#43566.

Code Example

snippet

# Check current installation method
file $(which claude)
# Result 'ELF 64-bit...' → native binary (has bugs)
# Result 'symbolic link...' → npm version (normal)

# Switch to npm
npm install -g @anthropic-ai/claude-code

# Check cache settings
cat ~/.claude.json | grep -A5 'cachedGrowthBookFeatures'

Terminology

캐시 TTL (Time To Live)The duration a cache remains valid. Claude Code can request either a 1-hour or 5-minute cache from the server; a 1-hour cache significantly reduces costs when the same context is sent repeatedly.

캐시 prefixAn identifier used to check whether an API request matches a previous context. If this value is corrupted or differs, a cache miss occurs and the full context is retransmitted and billed again.

AutocompactA Claude Code feature that automatically summarizes and compresses the session context when it grows too long. A bug existed where failed compression would retry infinitely due to the absence of a circuit breaker.

Extra UsageThe tier after exceeding the Claude Max plan's weekly quota, where additional charges apply per token. In this tier, per-token costs are incurred, and this bug simultaneously degrades cache efficiency.

I reverse-engineered why Claude Code burns through your usage so fast. 7 bugs that stack on top of each other — and the worst one activates when Extra Usage kicks in