You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and did not find a duplicate.
I am describing a concrete problem or use case, not just a vague idea.
Area
apps/web
Problem or use case
T3 Code does not show subscription usage the way Claude Code Desktop does.
In Claude Code Desktop, Settings → Usage (and the in-app usage panel) is a single glanceable view:
Current session — 5-hour rolling window, percent used, progress bar, reset countdown
Weekly · all models — percent used, progress bar, reset date/time
Extra rows when the plan has them (Sonnet-only, Claude Design, extra usage, …)
Last updated timestamp
Plan / account context
In T3 I have to leave the app (Claude Desktop, claude.ai/settings/usage, /usage in a side CLI) to know whether I can start a long run. Context-window meters are not the same thing as account quota.
#5539 already asks for remaining limits and reset times. This issue is the UX target: implement that view in Claude Code Desktop's Usage style, not a text dump or a single mystery percentage.
Proposed solution
Add a usage panel modeled on Claude Code Desktop's Usage tab.
Visual (match CC Desktop as closely as practical)
One card per usage bucket
Horizontal progress bar + percent used
Reset line under the bar (Resets in 2h 14m / Resets Wed 6:00 AM)
Bucket labels from the provider (Current session, Weekly · all models, model-specific rows)
Footer: Last updated … + manual refresh
Compact control near the provider/model picker that opens this panel; optional full page under Settings → Usage
Data
Prefer the same provider-reported buckets Claude Code already shows (/usage, Desktop Usage tab, auth/status payloads) — do not invent a percent from local token counts unless it is clearly labeled as an estimate.
Claude Code first (this is the design reference).
Codex / Cursor / other subscription providers next, with the same card layout whenever they expose comparable buckets (session + weekly is the common pair).
States
Live / stale / unavailable
Approaching limit and exhausted, named by bucket (not a generic banner)
Correct account when several environments share one login
Why this matters
Quota is what decides “can I start this agent now?” Claude Code Desktop already solved the glanceable version of that. T3 users on Claude/Cursor/Codex subscriptions currently keep Desktop or a browser tab open just to read bars and reset times (#5539 comments say the same). Matching that UI means people can stay in T3.
Smallest useful scope
One Usage popover or Settings section.
Claude Code only.
Desktop-style rows: Current session + Weekly · all models, each with a progress bar, percent, and reset time.
Manual refresh + last-updated.
Unavailable state if the CLI/SDK does not return quota.
This discussion was converted from issue #6582 on August 15, 2026 09:54.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/web
Problem or use case
T3 Code does not show subscription usage the way Claude Code Desktop does.
In Claude Code Desktop, Settings → Usage (and the in-app usage panel) is a single glanceable view:
In T3 I have to leave the app (Claude Desktop, claude.ai/settings/usage,
/usagein a side CLI) to know whether I can start a long run. Context-window meters are not the same thing as account quota.#5539 already asks for remaining limits and reset times. This issue is the UX target: implement that view in Claude Code Desktop's Usage style, not a text dump or a single mystery percentage.
Proposed solution
Add a usage panel modeled on Claude Code Desktop's Usage tab.
Visual (match CC Desktop as closely as practical)
Resets in 2h 14m/Resets Wed 6:00 AM)Current session,Weekly · all models, model-specific rows)Last updated …+ manual refreshData
/usage, Desktop Usage tab, auth/status payloads) — do not invent a percent from local token counts unless it is clearly labeled as an estimate.States
Why this matters
Quota is what decides “can I start this agent now?” Claude Code Desktop already solved the glanceable version of that. T3 users on Claude/Cursor/Codex subscriptions currently keep Desktop or a browser tab open just to read bars and reset times (#5539 comments say the same). Matching that UI means people can stay in T3.
Smallest useful scope
Alternatives considered
/usage/ claude.ai — works, splits attention.Risks or tradeoffs
Examples or references
/usageAll reactions