claude-code - 💡(How to fix) Fix [Bug] Unexpectedly high token usage since April 11th with unchanged workloads [2 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#49072Fetched 2026-04-17 08:51:42
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1cross-referenced ×1

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description Experiencing unexpectedly high token usage since Friday April 11th. Simple script execution commands that previously used minimal tokens are now consuming 18% of session usage. Multiple team members experiencing the same issue simultaneously. Using medium effort setting (unchanged from before). Issue appears to correlate with recent system incidents around April 15-16. Request investigation into token calculation accuracy and background process consumption during this timeframe.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.110
  • Feedback ID: 1b77c9ac-e334-455a-bb33-c155e323d6f0

Errors

[]

extent analysis

TL;DR

Investigate recent system incidents around April 15-16 for potential causes of increased token usage.

Guidance

  • Review system logs and incident reports from April 15-16 to identify any changes or issues that may be contributing to the increased token usage.
  • Verify that the medium effort setting is still configured correctly and has not been modified inadvertently.
  • Check for any background processes that may be consuming tokens unexpectedly, and investigate ways to optimize or disable them if necessary.
  • Consider temporarily adjusting the effort setting to a lower level to mitigate token usage while the investigation is ongoing.

Notes

The issue appears to be correlated with recent system incidents, but without more information about the incidents or the token calculation process, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Temporarily adjust the effort setting to a lower level to mitigate token usage while the investigation is ongoing. This may help reduce the immediate impact of the issue while the root cause is being investigated.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Bug] Unexpectedly high token usage since April 11th with unchanged workloads [2 comments, 2 participants]