Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude Opus 4.6 usage limit instantly maxed after 5-hour reset [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#46075•Fetched 2026-04-11 06:29:38
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
revengerrrrevengerrr
Participants
github-actions[bot]github-actions[bot]revengerrrrevengerrr
Timeline (top)
cross-referenced ×3labeled ×3commented ×1

Error Message

Error Messages/Logs

No explicit error message is shown.

Code Example

No explicit error message is shown.
The issue is observed via the usage meter:

5-hour usage instantly maxed
Weekly usage: 40% → 54% after two prompts
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?

After waiting for the 5-hour session reset, Claude Opus 4.6 usage is instantly maxed out after only two prompts. The reset appears to occur normally, but within ~2 minutes and two prompts:

The 5-hour session limit becomes fully used Weekly usage jumps from ~40% to ~54% Prompts were normal-sized (not unusually long or heavy)

This makes the quota unusable immediately after reset and seems inconsistent with expected token usage behavior.

What Should Happen?

After the 5-hour reset, usage should increase gradually based on prompt size and token consumption. Two normal prompts should not fully exhaust the 5-hour limit or significantly jump weekly usage.

Error Messages/Logs

No explicit error message is shown.
The issue is observed via the usage meter:

5-hour usage instantly maxed
Weekly usage: 40% → 54% after two prompts

Steps to Reproduce

Use Claude with Opus 4.6 Wait until the 5-hour usage session resets Send one normal prompt Send a second normal prompt within ~2 minutes Observe usage meter 5-hour session becomes fully used immediately Weekly usage increases disproportionately

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Not sure — previously this behavior did not occur with earlier Opus sessions.

Claude Code Version

Latest (exact version not checked)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Occurred immediately after session reset Only two prompts were sent No long context or file uploads Weekly usage increased unusually fast Happens specifically when using Opus 4.6 May be related to incorrect token accounting or quota calculation

extent analysis

TL;DR

The issue may be resolved by investigating and adjusting the token accounting or quota calculation for Claude Opus 4.6, as it appears to be incorrectly consuming the 5-hour session limit and disproportionately increasing weekly usage.

Guidance

  • Review the token consumption pattern for Claude Opus 4.6 to identify any discrepancies in quota calculation.
  • Verify that the issue is specific to Opus 4.6 by testing other models and versions.
  • Check for any recent changes in the Anthropic API or Claude Code that may be contributing to the incorrect token accounting.
  • Consider reaching out to the Anthropic API support team for assistance with troubleshooting the quota calculation issue.

Example

No code snippet is provided as the issue is related to the Anthropic API and Claude Code, and no specific code is mentioned.

Notes

The exact cause of the issue is uncertain, and further investigation is needed to determine the root cause. The issue may be related to a regression in the Claude Code or Anthropic API.

Recommendation

Apply workaround: The user may need to adjust their usage pattern or implement a temporary workaround, such as limiting the number of prompts sent immediately after the 5-hour session reset, until the root cause of the issue is identified and resolved.

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#environment setup#docker error#permission error#memory optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING