[FEATURE] Show subscription usage % in /cost for Pro/Max users

[kickenchicken7]

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

Claude Code's /cost command provides no actionable usage data for Pro and Max subscribers — it only confirms that a
subscription is active. However, the claude.ai web interface displays real-time daily and weekly usage percentages
drawn from the same account. This creates an inconsistency where users must leave the CLI and open a browser to check
how much of their usage limit remains, interrupting their workflow.

Proposed Solution

Extend the /cost (or /usage) command for Pro/Max subscribers to query and display the same usage metrics available
on the claude.ai dashboard — specifically the current daily and weekly usage as a percentage of the plan limit. This
would allow developers to monitor their remaining capacity without leaving the terminal.

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Anytime im working it would be helpful to see how much this session has affected my usage, so i can better plan which models i use for what.

Additional Context

No response

[github-actions]

Found 3 possible duplicate issues:

1. Feature request: command to show Pro plan usage percentage and daily/monthly limit #33364
2. Feature Request: Pro Plan 5-Hour Window Usage Visibility #9617
3. [FEATURE] Built-in Usage Analytics Command (claude usage) — Consolidates 10+ Open Issues #33978

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

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.