Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] macOS Desktop Code tab blocks new sessions when extra-usage cap is hit, despite plan quota remaining (iOS Code and macOS Chat unaffected) [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#52240•Fetched 2026-04-24 06:12:27
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
RanaCMRanaCM
Participants
github-actions[bot]github-actions[bot]RanaCMRanaCM
Timeline (top)
labeled ×4commented ×1cross-referenced ×1

The Code tab in the macOS Desktop app greys out the send button with an "Out of extra usage / Upgrade" banner when the monthly extra-usage spend cap is exhausted — even when the plan still has significant weekly quota remaining. The same account on iOS Code and macOS Chat is unaffected, which indicates the macOS Code tab is gating on extra-usage availability rather than actual plan quota.

Root Cause

The Code tab in the macOS Desktop app greys out the send button with an "Out of extra usage / Upgrade" banner when the monthly extra-usage spend cap is exhausted — even when the plan still has significant weekly quota remaining. The same account on iOS Code and macOS Chat is unaffected, which indicates the macOS Code tab is gating on extra-usage availability rather than actual plan quota.

Fix Action

Fix / Workaround

Impact

Users whose extra-usage cap is hit — often intentionally, to control spend — are locked out of the macOS Desktop Code tab even though their paid-plan quota is intact. The only workarounds are raising the extra-usage cap (forcing users to risk the overspend they deliberately capped) or switching to a different client.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues (related: #28096, #46812, #28450). This has a distinct symptom surface and diagnostic signal not captured there.
  • This is a single bug report.
  • I am using the latest version of the Claude Desktop app.

Platform

  • Claude Desktop app (macOS) — version 1.3883.0 (93ff6c)
  • Also tested on the same account at the same moment:
    • Claude iOS app — version v1.260409.1 (24361703904) → Code tab works
    • Claude Desktop (macOS) → Chat tab → works

Summary

The Code tab in the macOS Desktop app greys out the send button with an "Out of extra usage / Upgrade" banner when the monthly extra-usage spend cap is exhausted — even when the plan still has significant weekly quota remaining. The same account on iOS Code and macOS Chat is unaffected, which indicates the macOS Code tab is gating on extra-usage availability rather than actual plan quota.

Expected Behavior

With plan quota remaining, starting a new Claude Code session should succeed. Per the Help Center article on extra usage for paid plans, extra usage should only be consumed after plan limits are exhausted. Hitting the extra-usage spend cap should not block sessions that can be served by remaining plan quota.

Actual Behavior

SurfaceResult
macOS Desktop → Code tabSend button disabled, "Out of extra usage" banner, cannot start new session
macOS Desktop → Chat tabWorks normally
iOS Claude app → Code tabWorks normally

Same account, same moment, same backend state.

Usage State When Blocked

  • 5-hour limit: ~6% used (plenty of headroom)
  • Weekly · all models: ~86% used (headroom remaining)
  • Weekly · Claude Design: ~20% used
  • Sonnet only: ~14% used
  • Extra-usage monthly spend cap: exhausted (resets Friday 3:00 AM)

Steps to Reproduce

  1. Enable extra usage with a monthly spend cap.
  2. Exhaust the extra-usage cap (wait until the "Out of extra usage" state is active).
  3. Ensure plan quota (5-hour and weekly) still has headroom.
  4. Open Claude Desktop app on macOS → Code tab → new session → send button is greyed.
  5. Open iOS Claude app → Code tab → new session → sends work normally.
  6. Open Claude Desktop app on macOS → Chat tab → sends work normally.

Diagnostic Note

The asymmetry between surfaces on the same account rules out a backend account-state issue. The macOS Desktop Code tab appears to run a stricter client-side preflight that treats "extra-usage cap exhausted" as "no usage available," ignoring remaining plan quota. iOS Code and macOS Chat do not enforce this check.

Impact

Users whose extra-usage cap is hit — often intentionally, to control spend — are locked out of the macOS Desktop Code tab even though their paid-plan quota is intact. The only workarounds are raising the extra-usage cap (forcing users to risk the overspend they deliberately capped) or switching to a different client.

Related Issues

  • #28096 — CLI "Rate limit reached" despite quota remaining, after extra usage exhausted/disabled. Same root-cause family (extra-usage state gates access despite plan quota), different surface. This new report adds a cross-surface asymmetry signal (iOS Code works, macOS Desktop Code blocks) that points at a macOS-Desktop-client preflight rather than a purely server-side flag.
  • #46812 — Claude Code fully locked (no input box) after weekly limit with extra usage available. Different bug, referenced for completeness.
  • #28450 — Max plan rate-limited when Extra Usage toggle disabled (closed as duplicate of #28096).

extent analysis

TL;DR

The macOS Desktop Code tab may be fixed by adjusting the client-side preflight check to consider remaining plan quota when the extra-usage cap is exhausted.

Guidance

  • Investigate the client-side preflight logic in the macOS Desktop Code tab to determine why it treats an exhausted extra-usage cap as "no usage available," ignoring remaining plan quota.
  • Compare the preflight logic between the macOS Desktop Code tab, iOS Code tab, and macOS Chat tab to identify discrepancies.
  • Consider implementing a fix that allows the macOS Desktop Code tab to start new sessions when plan quota remains, even if the extra-usage cap is exhausted.
  • Verify that the fix does not introduce any security or billing vulnerabilities.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The issue appears to be specific to the macOS Desktop Code tab and may not affect other surfaces or clients. The fix should ensure that the client-side preflight check accurately reflects the user's available quota.

Recommendation

Apply a workaround by adjusting the client-side preflight check to consider remaining plan quota when the extra-usage cap is exhausted, as this is likely to resolve the issue without introducing significant risks.

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…
#indexing error#inference speed#output truncation#response parsing#generation 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