[FEATURE] Real-time plan usage/quota indicator in Cowork (5-hour & weekly limits)
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Cowork has no visible indicator of PLAN USAGE / QUOTA consumption. Users cannot
see how much of their 5-hour window or weekly limit they have consumed during a
session. The only way to check is to leave the session and open Settings > Usage
on claude.ai, which shows limited, non-real-time data.
Claude Code solves this: /usage shows current 5-hour and weekly consumption and
reset times. Cowork users get nothing equivalent and only find out they are near
the cap when a warning appears close to the limit.
IMPORTANT — this is NOT about the context window / compaction indicator. Existing
requests (#37568, #20041, #35374) all cover context-window usage and were closed.
This request is specifically about PLAN QUOTA (5-hour and weekly rate limits),
which is a different metric and remains unaddressed in Cowork.
Proposed Solution
- A persistent, always-visible indicator in the Cowork UI showing current 5-hour
and weekly quota consumption as a percentage, plus reset time.
- This is the same data
/usagealready exposes in the CLI — extend it to Cowork. - Optional: a warning threshold (e.g. 80%) so users can plan work before hitting
the cap.
Alternative Solutions
Currently users must leave the session and check Settings > Usage manually, or rely
on unofficial third-party tray apps that read internal endpoints — fragile and a
security concern. Neither is acceptable for a first-party workflow tool.
Priority
Medium - Would be very helpful
Feature Category
Interactive mode (TUI)
Use Case Example
Example scenario:
- I open a Cowork session to work through a multi-step task (research + document
generation) that spans 30-60 minutes.
- Partway through, my 5-hour quota runs out with no advance warning — the session
stops mid-task and I lose momentum.
- With a visible quota indicator, I would have seen I was near the cap and could
have paused, split the work, or waited for the reset instead of being cut off.
- This saves time because I can plan around the limit proactively instead of
discovering it reactively, the same way /usage already lets CLI users do.
Additional Context
- Claude Code already exposes this data via
/usage(5-hour and weekly consumption - reset times). The request is to surface the same data in the Cowork UI.
- Related closed issues cover the CONTEXT WINDOW indicator, not plan quota:
#37568, #20041, #35374. This request is a distinct metric and should not be
treated as a duplicate of those.
- Third-party tray apps exist but read internal endpoints — fragile and a security
concern for a first-party tool.