Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude Desktop (Windows) shows "Usage limit reached" with only 3% of 5-hour limit used - enterprise accounts cannot use cache-clear workaround [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#55544•Fetched 2026-05-03 04:50:39
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
SnehDungraniSnehDungrani
Participants
SnehDungraniSnehDungrani
Timeline (top)
labeled ×2renamed ×1unlabeled ×1

Error Message

Claude Desktop app (Windows) is showing "Usage limit reached" despite having minimal actual usage. The 5-hour usage counter shows only 3% used, yet the input is blocked and the error banner is displayed. This is a recurring issue — it also happened the previous day and was only resolved by clearing cache and restarting (which forced a sign-out).

Error Messages/Logs

Fix Action

Fix / Workaround

Claude Desktop app (Windows) is showing "Usage limit reached" despite having minimal actual usage. The 5-hour usage counter shows only 3% used, yet the input is blocked and the error banner is displayed. This is a recurring issue — it also happened the previous day and was only resolved by clearing cache and restarting (which forced a sign-out).

This is particularly problematic for users on company/enterprise accounts where re-authentication requires a one-time code or admin approval, making the cache-clear workaround impractical for repeated use.

Environment

  • Platform: Windows (Claude Desktop app)
  • Model shown: Opus 4.7 1M · Medium
  • Account type: Company/Enterprise
  • Workaround attempted: Clearing cache + restart (forces sign-out) — temporarily fixes it but not viable for repeated use on company accounts requiring auth codes

Code Example

Usage limit reached
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?

Claude Desktop app (Windows) is showing "Usage limit reached" despite having minimal actual usage. The 5-hour usage counter shows only 3% used, yet the input is blocked and the error banner is displayed. This is a recurring issue — it also happened the previous day and was only resolved by clearing cache and restarting (which forced a sign-out).

This is particularly problematic for users on company/enterprise accounts where re-authentication requires a one-time code or admin approval, making the cache-clear workaround impractical for repeated use.

Environment

  • Platform: Windows (Claude Desktop app)
  • Model shown: Opus 4.7 1M · Medium
  • Account type: Company/Enterprise
  • Workaround attempted: Clearing cache + restart (forces sign-out) — temporarily fixes it but not viable for repeated use on company accounts requiring auth codes
<img width="1069" height="338" alt="Image" src="https://github.com/user-attachments/assets/7bf96881-ce1c-448d-a91d-b1164fed95c3" />

What Should Happen?

Expected Behavior With only 3% of the 5-hour limit used, the app should be fully functional with no usage limit banner.

Actual Behavior App shows "Usage limit reached" and blocks all input despite low actual usage. The UI state appears stale/out of sync with the backend.

Error Messages/Logs

Usage limit reached

Steps to Reproduce

  1. Open Claude Desktop app (Windows)
  2. Do NOT send any messages (or minimal usage)
  3. Observe: "Usage limit reached" banner appears at the bottom
  4. Check Plan Usage panel — 5-hour limit shows ~3%, Weekly all models ~29%
  5. Input box is disabled/blocked

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.5220.0

Claude Code Version

Claude 1.5354.0 (9a9e3d) 2026-04-29T01:14:34.000Z

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

This appears to be a systemic state-sync issue between the usage tracking backend and the Windows desktop client. The web version (claude.ai) works correctly at the same time, suggesting the bug is desktop-app-specific. A fix that refreshes UI state without requiring full sign-out would be greatly appreciated, especially for enterprise users.

Related Issues

  • #52467 (Desktop app state-sync bug with extra usage)
  • #52249 (Desktop app shows Out of extra usage despite available balance)
  • #33120 (Rate limit triggered on every command regardless of actual usage)

extent analysis

TL;DR

The issue can be temporarily mitigated by clearing the cache and restarting the app, but a more permanent fix is needed to address the systemic state-sync issue between the usage tracking backend and the Windows desktop client.

Guidance

  • Investigate the difference in usage tracking between the web version and the desktop app to identify the root cause of the discrepancy.
  • Review the code changes between version 1.5220.0 (last working version) and 1.5354.0 (current version) to see if any changes may have introduced the bug.
  • Consider implementing a periodic refresh of the UI state to ensure it remains in sync with the backend usage tracking.
  • Examine the related issues (#52467, #52249, #33120) to see if there are any common patterns or fixes that can be applied to this issue.

Example

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

Notes

The issue appears to be specific to the Windows desktop app and may be related to a state-sync issue between the app and the backend usage tracking. The fact that the web version works correctly suggests that the issue is not with the backend itself, but rather with the desktop app's implementation.

Recommendation

Apply a workaround, such as periodically clearing the cache and restarting the app, until a more permanent fix can be implemented to address the state-sync issue. This is because upgrading to a fixed version is not currently an option, and the workaround can help mitigate the issue in the short term.

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#ssr#installation#tensor shape#request timeout

Still need to ship something?

×6

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

Back to top recommendations

TRENDING