Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude Desktop App (Code Tab): Usage indicator displays irrelevant plan limit (Claude Design %) instead of 5-hour/weekly limits [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#51827•Fetched 2026-04-23 07:43:55
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
jamesleoreyesjamesleoreyes
Participants
jamesleoreyesjamesleoreyes
Timeline (top)
labeled ×4

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?

⚠️ Note: This is a Claude Desktop app UI bug, not a Claude Code CLI bug. The Fin support bot directed me here to submit a bug report. The template fields below are filled out as accurately as possible for a Desktop app report.

The usage indicator in the Code tab (bottom toolbar, to the right of the model picker and reasoning effort selector) displays "Plan 46%". This figure is being pulled from the Claude Design weekly limit, not the limits relevant to Claude Code. The 5-hour rolling limit is at 2% and the standard weekly limit is at 10%. The indicator appears to be surfacing whichever plan limit has the highest usage percentage, regardless of whether that limit is relevant to the current product context.

<img width="390" height="106" alt="Image" src="https://github.com/user-attachments/assets/e9301ff8-4e81-47cf-8054-581f90433b7f" /> <br> <img width="543" height="319" alt="Image" src="https://github.com/user-attachments/assets/c35fd06a-9703-4457-b2a6-2fbd34fabf05" />

What Should Happen?

The Plan % in the Code tab should reflect the limits that actually govern Claude Code usage: the 5-hour rolling limit and/or the standard weekly limit. The Claude Design weekly limit is a separate, experimental quota with no bearing on Claude Code sessions. Displaying it as the primary Plan % figure is actively misleading, and a user glancing at "Plan 46%" will reasonably conclude they've consumed nearly half their plan, when their relevant limits are at 2% and 10%.

Error Messages/Logs

Steps to Reproduce

  1. Open Claude Desktop app and navigate to the Code tab
  2. Observe the usage indicator in the bottom toolbar
  3. Hover over the indicator to expand the usage breakdown
  4. Note that the collapsed "Plan XX%" figure matches the Claude Design weekly limit (the highest value shown), not the 5-hour or standard weekly limits

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Unknown

Claude Code Version

N/A — Claude Code CLI not involved; this is the Claude Desktop app

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

Screenshots attached showing "Plan 46%" in the tooltip, with the full breakdown visible: Claude Design weekly 46%, Weekly all models 10%, 5-hour limit 2%, Sonnet only 1%.

extent analysis

TL;DR

The usage indicator in the Code tab of the Claude Desktop app should be updated to reflect the relevant limits for Claude Code usage, rather than displaying the Claude Design weekly limit.

Guidance

  • Verify that the issue is indeed caused by the usage indicator pulling from the wrong limit by checking the code that updates the indicator and ensuring it is using the correct limits for Claude Code.
  • Check the API calls made by the Claude Desktop app to retrieve usage data and confirm that they are requesting the correct limits.
  • Update the code to prioritize displaying the 5-hour rolling limit and/or the standard weekly limit in the usage indicator, rather than the Claude Design weekly limit.
  • Test the updated code to ensure the usage indicator now accurately reflects the relevant limits for Claude Code usage.

Notes

The exact code changes required to fix the issue are not specified, as the codebase is not provided. However, the general approach should involve updating the usage indicator to use the correct limits for Claude Code.

Recommendation

Apply workaround: Update the code to prioritize displaying the relevant limits for Claude Code usage, as the current behavior is misleading and causing confusion for users.

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#cache issue#memory leak#API versioning#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