[FEATURE] Show rate-limiting stats in /stats (retention risk for Max subscribers)

Preflight Checklist

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

Problem Statement

Max subscribers have zero visibility into rate limiting. When I get paused, I don't know:

• How often it happens, unless I make notes on paper.
• How much cumulative time I've lost, unless I set up external tools to track this.
• Whether I'm consistently near the limit or just occasionally spiking (I can't figure this out at all!)

This matters because rate limits are the primary friction point for Max subscribers, and the decision to stay on Max
vs. upgrade (or cancel) is currently made on vibes rather than data. I've genuinely considered canceling because I
feel like I'm paused a lot, but I have no way to verify whether that's 20 minutes a week or 4 hours a day.

Without this data, Anthropic also can't benefit from the signal — you can't distinguish "churned because limits were
too tight" from "churned for unrelated reasons."

When I asked Claud it said "I don't believe /stats tracks rate-limit pauses. As far as I know, there's no built-in feature in Claude Code that logs when you get throttled. Might be worth filing as a feature request at https://github.com/anthropics/claude-code/issues — knowing when and how often you're hitting limits seems like useful info for Max subscribers."

──

So there you go. Claude sees the rationale in telling users that. Helps us, and helps you. Might make it easier to decide if Max is right or Max x2 or something is better for me.

Proposed Solution

/stats shows me what it currently does, but also shows me

• number of times I have been rate limited, and total hours when the product has basically been "offline" for me because my subscription is maxed until 8 PM PST. (So, 4 hours on that day)
• number of times I came within 5% of hitting a limit and being rate limited.

I honestly don't love the /stats view, it seems to be stuck on a year, when I really actually only want to see a week, but that's for ANOTHER Feature request since y'all don't believe in thinking about features holistically.

Alternative Solutions

_No response_

Priority

Non Critical - What /status does or doesn't do, is not blocking my work, but being paused IS blocking my work. I have thought of cancelling Claude max because it won't tell me what I want to know. I have a cursor and a github-copilot sub open because Claude Code maxxed out a few times, and I didn't want to make an upscale-decision that costs 2x what I'm currently spending just to keep working when I don't know how much value I will actually get.

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_