[FEATURE] Show extra usage spend and balance in the CLI when hitting rate limits

• [x] I searched existing issues and didn't find a duplicate
• [x] This is a single feature request

Problem Statement

When a user hits their Max plan rate limit and enables extra usage via /extra-usage, there is no visibility into how much money is being spent. The only notification is email receipts from Anthropic, which are not visible while actively working in the CLI.

Real-world scenario:

I'm on the Max 20x plan ($200/month). I had a runaway process consuming tokens in the background. When I hit the rate limit, I ran /extra-usage, got "Login successful", and continued working. The background process burned through the extra usage balance in seconds, capping me again almost immediately. I ran /extra-usage again, same result. This repeated several times.

The experience from my perspective:

1. Hit rate limit. Ran /extra-usage. Got "Login successful."
2. Claude still said "You're out of extra usage." (It was consumed before I could type a message.)
3. Repeated steps 1-2 multiple times, confused about why login kept succeeding but I was still capped.
4. Eventually accumulated $47.36 in extra usage charges before realizing what was happening.
5. When I asked Claude "how did I just burn through $47.36 in extra usage?" it could not answer because I was already capped again.

I only discovered the $47.36 total later when I checked my email and found five separate Anthropic receipts within a 30-minute window.

Proposed Solution

Show extra usage spend information directly in the CLI:

1. When hitting the rate limit: Display current extra usage spend for the period, e.g., "You've hit your limit. Extra usage spent this period: $47.36. Resets 10am (America/Denver)."

1. After /extra-usage login: Show remaining balance or spend-so-far, e.g., "Extra usage enabled. Spent so far: $47.36 this period."

1. Allow usage-related queries when capped: When a user asks about their usage or billing while capped, allow at least a lightweight response (perhaps via a smaller model or a system-generated message) rather than blocking entirely. Being charged $47 and then being unable to ask the system what happened is a frustrating catch-22.

Alternative Solutions

• Email receipts: These already exist but are not visible during active CLI work. They serve as a paper trail, not a real-time alert.
• Spending caps in account settings: These help prevent runaway costs but don't help the user understand what is happening in the moment.

Priority: Medium

Feature Category: CLI

Use Case Example

A user has a background process (e.g., a log-processing agent) that is consuming tokens without their knowledge. They hit the rate limit, enable extra usage, and the background process immediately eats through it. With spend visibility in the CLI, the user would see "Spent $20 in the last 4 minutes" and immediately know something is wrong, kill the runaway process, and avoid a $47 surprise.

Environment

• Claude Code Version: 2.1.87
• Claude Model: Opus 4.6 (1M context)
• Platform: Anthropic API (Max 20x subscription)
• Operating System: macOS 26.3.1 (Tahoe)
• Terminal/Shell: VS Code integrated terminal
• Machine: MacBook Pro, Apple M2 Pro, 16 GB
• VS Code: 1.113.0
• Claude Code Extension: 2.1.87