# Feature Request: Add Usage Metrics Transparency to Claude Code
## Summary
Claude Code should display real-time usage metrics to help users understand their current usage limits and which model (Opus 4 vs Sonnet 4) is
actively being used.
## Current Behavior
- No visibility into current usage percentage
- No indication when model switches from Opus 4 to Sonnet 4
- Users cannot plan their work based on remaining capacity
- Model switches happen silently at 20% usage threshold
## Desired Behavior
Claude Code should provide:
- Usage Dashboard showing:
- Current usage percentage (e.g., "15% of daily limit used")
- Active model indicator (e.g., "Currently using: Opus 4")
- Remaining capacity before model switch
- Status Indicators:
- Visual indicator in the interface showing active model
- Warning when approaching the 20% threshold
- Notification when model switch occurs
- Usage Commands:
/usagecommand to check current statistics/modelcommand enhancement to show why current model is active
## Benefits
- Better Planning: Users can prioritize complex tasks when Opus 4 is available
- Transparency: Users understand what's happening behind the scenes
- User Control: Ability to make informed decisions about task execution
- Improved Experience: No surprise model switches during critical work
## Proposed Implementation
- Add usage metrics to the session context
- Display metrics in the interface (status bar or dedicated panel)
- Include usage info in the
/modelcommand output - Optional: Allow users to set custom threshold warnings
## Example Interface
````
Claude Code Status:
Model: Opus 4 (15% of 20% limit used)
Daily Usage: 2.5k/15k tokens
Next Model: Sonnet 4 (after 20%)
## User Story
As a Claude Code user, I want to see my current usage metrics so that I can plan my work effectively and understand which model is serving my
requests.
---
This feature would significantly improve the Claude Code user experience by providing transparency about usage limits and model selection.
Showing cached comments. Read the full discussion on GitHub ↗
7 Comments
With the new weekly limits, this just became 10x more urgent.
Please. We can't even bypass it in cli.js anymore because it's more complex now.
+1000
Excellent feature request.
+1000, we need it
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.