Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Unexplained token consumption spike since early April with no change in usage pattern [1 comments, 2 participants]

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…
GitHub stats
anthropics/claude-code#52286•Fetched 2026-04-24 06:11:09
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
huneauhuneau
Participants
github-actions[bot]github-actions[bot]huneauhuneau
Timeline (top)
labeled ×4commented ×1unlabeled ×1

Error Message

Error Messages/Logs

Code Example

No errors — silent over-billing only visible on the usage dashboard.
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?

Starting around early April 2026, my daily token consumption increased dramatically with no change in how I use Claude Code. Same types of tasks, same repos, same session lengths, same prompts — but daily totals jumped from the ~100-400k tokens/day range I had sustained from December through late March, to repeated 2-3M tokens/day spikes.

The breakdown across models shows the increase on every model I use (Opus 4.6, Opus 4.7, Opus 4.5, Haiku 4.5, Sonnet 4.6), so it does not look tied to a single model's billing.

I have attached a screenshot of the Models tab from the usage dashboard (All range) showing the pattern clearly: flat baseline through Q1, sudden step-up starting ~Apr 10, sustained at 5-10× baseline since.

Nothing changed on my side: same machine, same workflows, same project sizes, no new heavy automation.

What Should Happen?

Token consumption should track actual usage. A 5-10× jump with no change in behavior suggests a billing or cache regression somewhere in the recent Claude Code releases.

Error Messages/Logs

No errors — silent over-billing only visible on the usage dashboard.

Steps to Reproduce

Not a reproducible single action — it is a sustained pattern visible on the usage dashboard. Happy to share anonymized session-level data if that helps the team.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.87

Claude Code Version

2.1.117

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

<img width="547" height="457" alt="Image" src="https://github.com/user-attachments/assets/25115931-502b-4d25-b153-1a2ee65c679c" />

extent analysis

TL;DR

The most likely fix is to investigate and potentially revert recent changes in the Claude Code releases that may be causing the sudden increase in token consumption.

Guidance

  • Review the changelog for Claude Code versions 2.1.88 to 2.1.117 to identify potential changes that could be causing the increased token consumption.
  • Compare the usage patterns and token consumption for the same period in the previous version (2.1.87) to confirm the regression.
  • Share anonymized session-level data with the development team to help them investigate the issue.
  • Consider reaching out to the Anthropic API support team to see if there were any changes to their billing or caching mechanisms that could be contributing to the issue.

Example

No code snippet is provided as the issue is related to token consumption and billing, which is not directly related to code.

Notes

The issue seems to be related to a regression in the Claude Code releases, and the exact cause is unclear. Further investigation is needed to determine the root cause of the issue.

Recommendation

Apply workaround: The user should consider reverting to the previous version (2.1.87) or waiting for a fix from the development team, as the current version (2.1.117) is causing unexpected token consumption.

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…
#api#prompt issue#agent setup#task chaining#parallel task

Still need to ship something?

×6

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

Back to top recommendations

TRENDING