[Feature]: Show subscription usage in Claude Code Desktop style

[boonguan]

Before submitting

• 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.

Alternatives considered

• [Feature]: Show remaining provider usage limits and reset times in the T3 Code UI #5539 — full data requirements for every provider. Still needed; this issue pins the visual to Claude Code Desktop so the first ship is recognizable rather than a one-line status.
• feat: add usage / quota visibility for Codex sessions and accounts #228 — Codex quota visibility; more account/session telemetry than a Desktop-style panel.
• Keep using Claude Code Desktop / /usage / claude.ai — works, splits attention.
• Reuse the context-window ring for quota — that ring is tokens-in-thread; mixing it with 5-hour/weekly quota is how those two numbers get confused.

Risks or tradeoffs

• Quota endpoints and labels change by plan; copy them from the provider, do not hard-code bucket names.
• Do not scrape claude.ai HTML.
• Conservative refresh (startup, account change, after turns, manual) so T3 does not add extra quota traffic.
• Usage is account-sensitive; same auth boundary as the provider session.

Examples or references

• Design reference: Claude Code Desktop → Settings → Usage (progress bars, session + weekly + extra buckets, last updated)
• Claude Code CLI: /usage
• [Feature]: Show remaining provider usage limits and reset times in the T3 Code UI #5539 — remaining provider usage limits and reset times (data/requirements; this issue is the Desktop-style UX)
• feat: add usage / quota visibility for Codex sessions and accounts #228 — Codex usage / quota visibility

[Bibendus83]

Any update on this?

[orowebregen]

Yes, I also wish this existed. I find myself doing this often and would love to see this all inside of the T3 Code app.