claude-code - 💡(How to fix) Fix [BUG] Desktop app shows "Out of extra usage" and disables input despite 91% weekly / 61% extra usage remaining [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#52249Fetched 2026-04-24 06:12:12
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Timeline (top)
labeled ×4cross-referenced ×2commented ×1subscribed ×1

Error Message

API Error: Prompt is too long ⚡ Out of extra usage [Upgrade]

Root Cause

Related issues: #51442, #50237, #46812 — similar symptoms but different root cause. Those report "Usage limit reached" while this specifically traces the trigger to a "Prompt is too long" error corrupting the usage state across all sessions.

Code Example

API Error: Prompt is too long
Out of extra usage [Upgrade]
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?

OS: Windows 11 Pro 10.0.26200 App version: Claude Code v2.1.108 Plan: Claude Max (5x) Exact error: "Out of extra usage" banner at bottom of chat, input box is completely disabled (cannot type)

Usage at time of bug:

  • Current session: 4% used
  • Weekly All models: 91% used (resets in 17hr)
  • Sonnet only: 5% used
  • Extra usage: $303.04 / $500 (61% used), balance $49.99, auto-reload on

Key evidence this is a bug, not a real limit:

  1. Claude Code CLI (terminal) works perfectly fine on the same account at the same time
  2. Weekly usage is only 91%, not 100%
  3. Extra usage has $197 remaining budget and $49.99 balance
  4. Creating a new session in the desktop app also shows the same error — input is disabled across ALL sessions, not just the one that hit "Prompt is too long"

Sequence of events:

  1. Was using desktop app normally in a long session
  2. One session hit "API Error: Prompt is too long" (context grew too large)
  3. After that error, the app started showing "Out of extra usage" on that session
  4. Tried opening a new session — same "Out of extra usage", cannot type
  5. Rebooted the entire PC — same issue persists
  6. Claude Code CLI works fine on the same account simultaneously

This appears to be a UI state bug where the "Prompt is too long" API error incorrectly triggers the "Out of extra usage" lockout state, and that state persists across all sessions including new ones, even after a full reboot.

What Should Happen?

  1. "Prompt is too long" should NOT trigger "Out of extra usage" — these are different errors
  2. Even if one session's context is too large, new sessions should work normally
  3. The input box should never be disabled when the user has remaining usage quota

Error Messages/Logs

API Error: Prompt is too long
⚡ Out of extra usage [Upgrade]

Steps to Reproduce

  1. Use Claude Desktop app on Max (5x) plan with extra usage enabled
  2. Have a very long conversation until "Prompt is too long" API error appears
  3. Observe that the input box becomes disabled with "Out of extra usage"
  4. Try creating a new session — input is still disabled
  5. Reboot PC — issue persists
  6. Verify Claude Code CLI works fine on the same account

Claude Model

Sonnet 4.6 / High

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

v2.1.108

Platform

Claude Max

Operating System

Windows 11 Pro

Terminal/Shell

N/A (Desktop app issue)

Additional Information

Related issues: #51442, #50237, #46812 — similar symptoms but different root cause. Those report "Usage limit reached" while this specifically traces the trigger to a "Prompt is too long" error corrupting the usage state across all sessions.

extent analysis

TL;DR

The "Out of extra usage" error may be incorrectly triggered by the "Prompt is too long" API error, causing the input box to be disabled across all sessions.

Guidance

  • Verify that the issue is specific to the desktop app by continuing to test the Claude Code CLI, which seems to work fine.
  • Try resetting the app's state by clearing local storage or cache, as the issue persists even after a reboot.
  • Check for any similar issues in the related reports (#51442, #50237, #46812) to see if there are any common patterns or workarounds.
  • Test creating a new session with a short prompt to see if the issue is indeed triggered by the "Prompt is too long" error.
  • Consider reaching out to the developers or support team to report the issue and ask for further assistance, as this may be a regression bug.

Notes

The issue seems to be specific to the desktop app and is triggered by the "Prompt is too long" API error. The fact that the Claude Code CLI works fine on the same account suggests that the issue is not related to the account's usage limits.

Recommendation

Apply workaround: Try resetting the app's state or testing with a short prompt to see if the issue can be temporarily resolved while waiting for a fix from the developers.

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