Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Usage limit reached despite UI showing low consumption percentages

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…

Error Message

Error Messages/Logs

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?

Summary

Claude Code displays "Usage limit reached" while the Plan Usage UI simultaneously shows very low consumption across all tracked metrics. The displayed percentages are clearly inconsistent with the actual enforcement happening under the hood.

What's Wrong?

The Claude Code interface blocked all usage (both Opus 4.7 and Sonnet 4.6) while the Plan Usage panel showed:

  • 5-hour session limit: ~1% used
  • Weekly · all models: ~17% used
  • Weekly · Claude Design (Opus): ~34% used
  • Weekly · Sonnet only: ~17% used

None of these values are near 100%, yet the system returned a hard block with "Usage limit reached" and an Upgrade prompt. Switching from Opus 4.7 to Sonnet 4.6 did not resolve the issue — confirming this is not a model-specific limit.

Actual Behavior

Hard block on all usage. UI percentages appear to be decorative rather than accurately reflecting actual enforcement state.

What Should Happen?

Usage limits should be enforced consistently with what the UI displays. If the 5-hour session is at 1% and weekly limits are at 17%, the user should not be blocked.

Error Messages/Logs

Steps to Reproduce

  1. Open Claude Code (desktop app)
  2. Check Plan Usage panel — all metrics show low percentages
  3. Attempt to send any message (any model)
  4. Receive "Usage limit reached" block despite UI showing available headroom

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Sonnet 4.6

Claude Code Version

Latest

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Warp

Additional Information

This makes it impossible to plan or manage usage effectively. If the displayed metrics cannot be trusted, the entire usage tracking UI is misleading paying subscribers. Related to #11810 and #9094 — this issue appears to still be actively affecting users.

extent analysis

TL;DR

The "Usage limit reached" block may be caused by a discrepancy between the displayed usage metrics and the actual enforcement state, requiring a review of the usage tracking and limit enforcement mechanisms.

Guidance

  • Verify the calculation and updating of usage metrics in the Plan Usage panel to ensure they accurately reflect the current usage state.
  • Investigate the enforcement logic for usage limits to determine why it's blocking usage despite the UI showing available headroom.
  • Check for any recent changes to the usage tracking or limit enforcement code that may have introduced this inconsistency.
  • Consider temporarily disabling the usage limit enforcement to allow users to continue using the service while the issue is being investigated.

Example

No code snippet is provided as the issue does not contain sufficient technical details to create a specific example.

Notes

The issue appears to be a regression, and the fact that it worked in a previous version (Sonnet 4.6) suggests that a recent change may have introduced the problem. The relationship to issues #11810 and #9094 may indicate a broader problem with the usage tracking and limit enforcement mechanisms.

Recommendation

Apply workaround: Temporarily disable usage limit enforcement to allow users to continue using the service while the issue is being investigated, as the current implementation is causing unnecessary blocks and mistrust in the usage tracking UI.

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#authentication setup#request error#file not found#serialization error

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 limit reached despite UI showing low consumption percentages