Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Token inflation bug (v2.1.100+) — still present in v2.1.137? Two Max 20x accounts exhausted

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Running Claude Code v2.1.137 on macOS. Exhausted two separate Max 20x accounts ($400 total) within normal working sessions. Burn rate suggests the ~20K token inflation bug reported in #46917 may still be present in v2.1.137, despite the reported fix in v2.1.116.

What Should Happen?

Token consumption should match actual usage. Per #46917, v2.1.98 consumed ~50K cache_creation_input_tokens per session. v2.1.100+ inflated this to ~70K. Two Max 20x accounts should not be exhausted in normal daily Claude Code sessions.

Error Messages/Logs

Steps to Reproduce

  1. Install Claude Code v2.1.137 (native binary via ~/.claude/local/)
  2. Run normal Claude Code sessions on a medium-sized codebase
  3. Monitor usage limits — limits exhaust significantly faster than expected for Max 20x plan

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.98

Claude Code Version

2.1.137

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Requesting confirmation whether token inflation is resolved in v2.1.137, and usage credit review given two Max 20x accounts were exhausted — likely accelerated by this bug. Reference: #46917. Anthropic previously reset all subscriber limits on April 23 for earlier related incidents.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#environment setup#docker error#permission error#memory optimization#batch processing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING