Feature request: Expose usage/rate-limit metrics so users can make informed plan decisions
Resolved 💬 2 comments Opened Apr 12, 2026 by saitoko Closed May 23, 2026
Is your feature request related to a problem?
When I hit the rate limit on my current plan (e.g. Pro 5x), there's no way to review my usage history or patterns. This makes it difficult to decide whether to upgrade, downgrade, or stay on the current plan.
Describe the solution you'd like
Provide access to usage metrics, for example:
- Usage dashboard: Historical token/message usage over time (daily/weekly/monthly)
- Rate limit events: Timestamps of when rate limits were hit
- API headers or endpoint: A way for tools like Claude Code to programmatically read remaining quota (e.g.
x-ratelimit-remainingexposed to the session, or a dedicated API endpoint)
Why this matters
- Users can't make data-driven decisions about plan upgrades without visibility into their actual usage patterns
- Knowing when and how often rate limits are hit helps determine if a higher tier is worth the cost
- Currently the only signal is "it stopped working", with no historical context
Additional context
- Current plan: Pro 5x
- Use case: Claude Code (CLI / web) for daily software engineering tasks
- Date: 2026-04-12
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗