Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] Usage spike after rate limit reset with resumed session [1 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#46310•Fetched 2026-04-11 06:23:40
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
chrisfazzio1-sourcechrisfazzio1-source
Participants
chrisfazzio1-sourcechrisfazzio1-source
Timeline (top)
labeled ×3

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description When I run out of usage for the 5 hour limit, I sometimes leave the cluade console open while I wait for the limit to reset, I noticed twice today that after I resume in the console, my usage jumped 15-25% in 1 minute.. I'm on the max plan and it's impossible for me to do this naturally even while the 1 console claude session is constantly doing stuff.. So I feel like it has to be bug where its taking the usage from my previous context and pushing it into the new reset usage.. Btw, I did not wait for claude to tell me i ran out of usage and to wait for the limit to reset. I just stopped before the message showed, and resume after I knew the useage limit reset. I looked at my usage limit on the website and instantly it was 15-25% in 1 minute.

Environment Info

  • Platform: win32
  • Terminal: null
  • Version: 2.1.81
  • Feedback ID: 6d99c84d-961f-4ca5-8870-22a138995e3b

Errors

[]

extent analysis

TL;DR

The issue may be resolved by waiting for the "out of usage" message from Claude before stopping and resuming the console session.

Guidance

  • Verify that the usage jump occurs consistently when resuming the console session without waiting for the "out of usage" message.
  • Try waiting for the "out of usage" message from Claude before stopping and resuming the console session to see if it prevents the usage jump.
  • Check the usage limit on the website immediately after resuming the console session to confirm the usage jump.
  • Consider reporting this issue with more detailed steps to reproduce, as it may be a bug in the usage tracking mechanism.

Notes

The exact cause of the issue is unclear, but it appears to be related to the way usage is tracked when resuming a console session after reaching the usage limit.

Recommendation

Apply workaround: wait for the "out of usage" message from Claude before stopping and resuming the console session, as this may prevent the usage jump and provide more accurate usage tracking.

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…
#cache error#pipeline error#runtime error#dependency conflict#environment setup

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] Usage spike after rate limit reset with resumed session [1 participants]