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
#6582 shipped subscription usage as its own view. What is still missing is the glanceable part: the number I actually need is "how much of my 5-hour window is left", and I need it at the moment I am about to hit send — not after navigating to a separate page.
The composer already has a toolbar right under the input with the things that decide the cost of the next turn:
✳ Claude Opus 4.8 ⌄ | High ⌄ | 🔓 Full access ⌄
Model, reasoning effort, permission mode — all three are "what will this turn cost / how far will it go" controls. Remaining quota belongs in that same row. Today it is the one input to that decision that lives somewhere else, so the flow is: pick model → pick effort → leave the composer → come back → send.
Proposed solution
Add a fourth compact control to the composer toolbar, styled like the existing pickers.
Collapsed (default)
One chip: bucket + percent, e.g. Session 62% or a small bar + 62%
Shows the most-constraining bucket (usually the 5-hour session window; weekly if weekly is closer to exhaustion)
Colour follows the existing warning treatment as it approaches the limit
Expanded (click)
Popover with the buckets already modeled for the Usage page — Current session, Weekly · all models, plus model-specific rows when the plan has them
Progress bar, percent, reset time per row
Last updated … + manual refresh
Link to the full Usage page
Scope
Claude provider only for the first ship. Other providers get the same chip when they expose comparable buckets; hide it entirely when the provider reports nothing.
Reuse the data the Usage page already fetches — no new polling loop, no separate source of truth.
Why this matters
Quota is a per-turn decision, and the composer toolbar is where per-turn decisions are already made. A settings page answers "how am I doing this week"; a toolbar chip answers "can I send this one". Those are different questions and only the second one is blocking.
Smallest useful scope
Claude only.
One chip showing the single most-constraining bucket, percent only.
Click opens the existing Usage view (a popover can come later).
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.
Problem or use case
#6582 shipped subscription usage as its own view. What is still missing is the glanceable part: the number I actually need is "how much of my 5-hour window is left", and I need it at the moment I am about to hit send — not after navigating to a separate page.
The composer already has a toolbar right under the input with the things that decide the cost of the next turn:
✳ Claude Opus 4.8 ⌄ | High ⌄ | 🔓 Full access ⌄Model, reasoning effort, permission mode — all three are "what will this turn cost / how far will it go" controls. Remaining quota belongs in that same row. Today it is the one input to that decision that lives somewhere else, so the flow is: pick model → pick effort → leave the composer → come back → send.
Proposed solution
Add a fourth compact control to the composer toolbar, styled like the existing pickers.
Collapsed (default)
Session 62%or a small bar +62%Expanded (click)
Current session,Weekly · all models, plus model-specific rows when the plan has themLast updated …+ manual refreshScope
Why this matters
Quota is a per-turn decision, and the composer toolbar is where per-turn decisions are already made. A settings page answers "how am I doing this week"; a toolbar chip answers "can I send this one". Those are different questions and only the second one is blocking.
Smallest useful scope
Alternatives considered
Risks or tradeoffs
Examples or references
/usageArea: apps/web. Originally opened as #8518; moved here per CONTRIBUTING (feature requests belong in Ideas).
All reactions