claude-code - 💡(How to fix) Fix [BUG] Claude for Windows desktop app does not switch to extra usage when 5-hour limit is reached, while Claude Code CLI on the same account does [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#52467Fetched 2026-04-24 06:06:27
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×2commented ×1unlabeled ×1

Error Message

When I hit my 5-hour session limit, the Claude for Windows desktop app (v1.3883.0) shows the blocking error "Usage limit reached · resets at 5:40 PM · Upgrade" and disables the input box. This happens across all sessions, including new ones, and persists after fully quitting the app from the system tray, signing out and back in, and restarting the machine. Unlike #52249 (which traces the trigger to a "Prompt is too long" API error corrupting state on a Max 5x plan), in my case there was no preceding "Prompt is too long" error — the lockout occurred on normal 5-hour window expiry on a Pro plan.

Error Messages/Logs

  • #52249 — same family ("desktop app blocks despite available extra usage") but different trigger and different plan tier (Max 5x, post-"Prompt is too long" error). My case is on Pro plan with no preceding context-length error.

Code Example

Banner shown in Claude for Windows desktop app:
"Usage limit reached · resets at 5:40 PM   [Upgrade]"

Banner shown in Claude Code CLI (PowerShell, same account, same moment):
"Now using extra usage"
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?

Note: This bug is in the Claude for Windows desktop app, not Claude Code CLI. Filing here based on precedent of other Desktop bugs accepted in this repo (#48281, #50437, #48697, #50856).

I have extra usage enabled on my Claude Pro account with $83.10 prepaid balance and "Unlimited" monthly spend limit (configured via Settings > Usage on claude.ai web; $58.05 already spent this cycle, confirming the extra usage billing path works for my account).

When I hit my 5-hour session limit, the Claude for Windows desktop app (v1.3883.0) shows the blocking error "Usage limit reached · resets at 5:40 PM · Upgrade" and disables the input box. This happens across all sessions, including new ones, and persists after fully quitting the app from the system tray, signing out and back in, and restarting the machine.

On the exact same account, at the exact same moment, Claude Code CLI (v2.1.62) launched from PowerShell on the same Windows machine correctly shows "Now using extra usage" in its status bar and continues working without interruption.

So the extra usage mechanism itself works on the backend — the bug is that Claude for Windows is not honoring the extra usage flag for this account and is blocking the user as if extra usage were disabled.

Unlike #52249 (which traces the trigger to a "Prompt is too long" API error corrupting state on a Max 5x plan), in my case there was no preceding "Prompt is too long" error — the lockout occurred on normal 5-hour window expiry on a Pro plan.

What Should Happen?

When extra usage is enabled and there is available prepaid balance, the Claude for Windows desktop app should display "5-hour limit resets [time] - continuing with extra usage" (per https://support.claude.com/en/articles/12466728) and continue accepting messages, consistent with the behavior of Claude Code CLI on the same account at the same time.

Error Messages/Logs

Banner shown in Claude for Windows desktop app:
"Usage limit reached · resets at 5:40 PM   [Upgrade]"

Banner shown in Claude Code CLI (PowerShell, same account, same moment):
"Now using extra usage"

Steps to Reproduce

  1. Have a Claude Pro plan with extra usage enabled and prepaid balance > $0 (configured on claude.ai web → Settings → Usage; toggle ON, monthly spend limit set to "Unlimited").
  2. Use Claude for Windows v1.3883.0 until the 5-hour session limit is reached.
  3. Observe: blocking banner "Usage limit reached · resets at [time] · Upgrade" appears at the bottom of the chat. Input box becomes disabled.
  4. Open a new conversation in the desktop app — input is still disabled, same banner.
  5. Fully quit Claude for Windows from system tray (right-click → Quit, not just close window). Reopen. Same banner.
  6. Sign out via Settings → Sign out. Sign back in. Same banner.
  7. Restart the machine. Same banner.
  8. On the same machine, same account, run claude in PowerShell. Observe: status bar shows "Now using extra usage". CLI accepts prompts and works normally.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

Claude for Windows v1.3883.0 (93ff6c) Claude Code CLI v2.1.62 (working correctly on same account, included for contrast)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Related issues:

  • #52249 — same family ("desktop app blocks despite available extra usage") but different trigger and different plan tier (Max 5x, post-"Prompt is too long" error). My case is on Pro plan with no preceding context-length error.
  • #45192 — describes the broader pattern of dashboard/client usage state being out of sync on Windows.
  • #50856 — precedent for filing Claude Desktop bugs in this repo per Anthropic Fin support guidance.

The pattern across these issues suggests a systemic state-sync problem between the usage tracking backend and the Windows clients, where the desktop app appears more frequently affected than the CLI.

Screenshots attached:

  1. claude.ai Settings > Usage panel showing extra usage enabled, $58.05 spent, Unlimited monthly cap, $83.10 prepaid balance.
  2. Claude for Windows v1.3883.0 showing "Usage limit reached · resets at 5:40 PM · Upgrade" banner with input disabled.
  3. PowerShell running Claude Code CLI v2.1.62 on the same account at the same time, showing "Now using extra usage" in the status bar.
<img width="1464" height="612" alt="Image" src="https://github.com/user-attachments/assets/c77edc23-4691-42c9-97b2-6ceaaffa2ef9" /> <img width="1338" height="896" alt="Image" src="https://github.com/user-attachments/assets/9e06c6bb-c26c-41cb-9888-24ff40350718" /> <img width="1338" height="387" alt="Image" src="https://github.com/user-attachments/assets/5878a1b9-6522-4ed0-8997-e3e35e2041ea" /> <img width="1304" height="232" alt="Image" src="https://github.com/user-attachments/assets/47e2cfe7-2830-4ceb-bc09-ef29cf01d667" />

extent analysis

TL;DR

The Claude for Windows desktop app is not honoring the extra usage flag, causing it to block the user when the 5-hour session limit is reached, despite having available prepaid balance.

Guidance

  • Verify that the extra usage setting is correctly configured on the claude.ai web settings and that the prepaid balance is sufficient.
  • Compare the behavior of the Claude for Windows desktop app with the Claude Code CLI on the same account to confirm the discrepancy.
  • Check for any similar issues or patterns in the related issues (#52249, #45192, #50856) that may indicate a systemic state-sync problem between the usage tracking backend and the Windows clients.
  • Consider testing with a different plan tier or account settings to isolate the cause of the issue.

Example

No code snippet is provided as this issue appears to be related to the application's configuration and backend interaction rather than a specific code problem.

Notes

The issue may be related to a systemic state-sync problem between the usage tracking backend and the Windows clients, as suggested by the pattern across related issues. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround by using the Claude Code CLI instead of the desktop app until the issue is resolved, as it appears to be working correctly with extra usage enabled.

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] Claude for Windows desktop app does not switch to extra usage when 5-hour limit is reached, while Claude Code CLI on the same account does [1 comments, 2 participants]