claude-code - 💡(How to fix) Fix [BUG] 5h session limit after using commands like /context and /usage [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#53257Fetched 2026-04-26 05:20:21
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×1renamed ×1

Error Message

[{"error":"Error: 429 {"type":"error","error":{"type":"rate_limit_error","message":"This request would exceed your account's rate limit. Please try again later."},"request_id":"req_011CaQZucUyZQcSB5CXrhNci"}\n at generate (B:/~BUN/root/src/entrypoints/cli.js:11:55098)\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T13:28:19.739Z"}]

Code Example

[{"error":"Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"This request would exceed your account's rate limit. Please try again later.\"},\"request_id\":\"req_011CaQZucUyZQcSB5CXrhNci\"}\n    at generate (B:/~BUN/root/src/entrypoints/cli.js:11:55098)\n    at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:4943)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T13:28:19.739Z"}]
RAW_BUFFERClick to expand / collapse

Bug Description Hi, I need to speak with Product Support — I'm experiencing what I believe is a serious bug.

I opened a brand new session with the sole intention of checking my token usage, as recommended. I ran:

  • /context (once)
  • /usage (twice)

That's the entirety of my session activity. After just these three commands, I hit the 5-hour session limit. I hadn't done any actual work yet.

This is completely unacceptable. These are basic diagnostic commands built into the product — they are literally what's recommended for understanding token consumption. If running them burns through an entire session limit, something is fundamentally broken.

Please do not reply with links to documentation. I literally cannot open them — I don't have enough tokens left. That's the whole point of my complaint.

I want this escalated to someone who can actually investigate the session limit calculation and explain what happened. This needs to be fixed.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.119
  • Feedback ID: df295ad4-afa5-4ad0-901c-40fddd0f5b76

Errors

[{"error":"Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"This request would exceed your account's rate limit. Please try again later.\"},\"request_id\":\"req_011CaQZucUyZQcSB5CXrhNci\"}\n    at generate (B:/~BUN/root/src/entrypoints/cli.js:11:55098)\n    at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:4943)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T13:28:19.739Z"}]

extent analysis

TL;DR

The issue may be related to incorrect session limit calculation, and escalating the issue to Product Support for further investigation is necessary.

Guidance

  • The error message indicates a rate limit error, which suggests that the session limit is being exceeded unexpectedly.
  • The fact that running basic diagnostic commands burns through the entire session limit implies a potential issue with the session limit calculation or the commands themselves.
  • To mitigate the issue, it may be helpful to try running the commands separately, rather than in quick succession, to see if the session limit is still exceeded.
  • The provided error log and environment information should be shared with Product Support to aid in their investigation.

Notes

The issue lacks detailed information about the session limit calculation and the expected behavior of the diagnostic commands, making it difficult to provide a more specific solution.

Recommendation

Apply workaround: Escalate the issue to Product Support for further investigation, as they can review the session limit calculation and provide a more detailed explanation of the issue.

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] 5h session limit after using commands like /context and /usage [1 comments, 2 participants]