[Bug] Excessive token consumption compared to previous versions

Status Fixed / completed
Reported on v2.1.81
Maintainer reply None cached
Activity 7 comments · opened Apr 1, 2026 · closed Apr 14, 2026

Bug Description
The token consumption is very high these days compared to before

Environment Info

  • Platform: darwin
  • Terminal: WarpTerminal
  • Version: 2.1.81
  • Feedback ID: 19f6b1a2-e53c-4b54-9c88-bf5de5a7f049

Errors

[]

View original on GitHub ↗

7 Comments

jbj338033 · 5 months ago

same issue

ArkNill · 5 months ago

+1. Max 20, v2.1.89. April 1: 100% in ~70 min after reset. Same light workflow that worked for months.

Full report: #41788
Related: #38335, #38239, #40790, #6457, #40895, #41055, #38345, #41174, #41550, #41617, #41663, #41666, #41802

ashwin-cb · 5 months ago

Same issue!

ArkNill · 5 months ago

I've been experiencing the same issue on Max 20 ($200/mo) — rate limit 100% exhausted in ~70 minutes.

After setting up a monitoring proxy using the official ANTHROPIC_BASE_URL env var, I identified two cache bugs as the root cause (#40524, #34629) and measured the impact: cache read ratio dropped to 4.3%, meaning ~20x token inflation per turn. After applying workarounds it stabilized at 89-99%.

Full analysis with per-request measured data, safe workarounds, and community references (including cc-cache-fix): https://github.com/ArkNill/claude-code-cache-analysis

ArkNill · 5 months ago

Update (April 2): v2.1.90 has significantly improved cache efficiency — benchmark shows 95-99% cache read in stable sessions (both npm and standalone installations).

If you're still affected:

  1. Update: claude update (or npm install -g @anthropic-ai/claude-code)
  2. Pin the version: add "DISABLE_AUTOUPDATER": "1" to ~/.claude/settings.json env section
  3. Avoid --resume (still broken)

Note: server-side quota issues (org-level pool sharing, accounting mismatches) remain unresolved — the above fixes the client-side cache drain only.

Benchmark data: https://github.com/ArkNill/claude-code-cache-analysis

ArkNill · 4 months ago

April 3 update: v2.1.91 fixes the cache regression that caused the worst drain. If you are still hitting limits after updating, there are additional unfixed mechanisms: a 200K tool result budget cap, a client-side false rate limiter, and silent context stripping — all confirmed via proxy testing. Anthropic acknowledged peak-hour tightening on X (Lydia Hallie) but stated "none were over-charging you." Measured data and analysis: claude-code-cache-analysis

github-actions[bot] · 4 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.