[BUG] # Issue: Misleading Cost Command Output in Claude Code

Issue: Misleading Cost Command Output in Claude Code

Description

The /cost command in Claude Code displays incorrect information about Claude Max subscription limits, leading to user confusion when actual usage limits are reached.

Current Behavior

When running the cost command, Claude Code displays:

With your Claude Max subscription, no need to monitor cost — your subscription includes Claude Code usage

Actual Behavior

Despite this message, Claude Max subscribers do encounter usage limits and receive error messages such as:

Claude Max usage limit reached. Your limit will reset at 4pm.

To continue immediately, upgrade to a higher plan https://claude.ai/upgrade/max or
switch to a Console Account for credit based billing with higher limits • /login

Problem

This creates a contradictory user experience where:

1. The cost command suggests unlimited usage
2. Users actually hit limits during intensive coding sessions
3. Users receive confusing messaging about their subscription capabilities

Suggested Fix

Update the cost command output to accurately reflect Claude Max limitations:

Option 1 - Honest messaging:

Claude Max subscription includes Claude Code usage with daily/hourly rate limits. 
Current usage: [X]% of daily limit
Next reset: [time]

Option 2 - Helpful guidance:

Claude Max subscription covers Claude Code usage. You may encounter rate limits during intensive sessions.
Use `claude status` to check current usage levels.

Option 3 - Transparent limits:

Claude Max includes Claude Code with usage limits:
- Rate limits: [X] requests/hour  
- Daily limits: [Y] tokens/day
Current status: [usage info]

Impact

• Reduces user confusion about subscription capabilities
• Sets appropriate expectations for intensive development sessions
• Improves trust through accurate information
• Helps users plan their usage accordingly

User Experience

Users should be able to understand their actual limits and plan development work accordingly, rather than being surprised by unexpected limit messages after being told there are no limits to monitor.

Environment

• Claude Code CLI
• Claude Max subscription
• Intensive development sessions with multiple file operations

Reproduction

1. Have Claude Max subscription
2. Run cost command - see "no need to monitor" message
3. Use Claude Code intensively for extended session
4. Hit actual usage limits despite reassuring cost message