Feature request: historical usage-limit exhaustion count + timeline for Max/Pro accounts

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 16, 2026

What I'm trying to do

As a Max subscriber I want to see how many times I've hit my usage limits over time — both the 5-hour (daily) window and the weekly window — not just where I stand in the current window.

Right now /usage (and the claude.ai usage page) only shows the current window: how much of this window I've consumed and when it resets. Once a window rolls over, that information is gone. There's no way to answer basic questions like:

  • How many times did I exhaust my weekly limit last month?
  • How often am I hitting the 5-hour limit, and on which days?
  • Is my usage trending up week over week?

I went looking for this locally (~/.claude/stats-cache.json, telemetry, session transcripts) and confirmed none of it is persisted anywhere I can reach — the count genuinely only lives on Anthropic's side, so this has to come from the product.

The feature request

Expose a historical record of limit-exhaustion events with a timeline, for Max/Pro subscription accounts. Concretely:

  1. A count of limit hits over a chosen period — e.g. "5-hour limit reached 12× in the last 30 days; weekly limit reached 2×."
  2. A timeline / history, not just a running total — each exhaustion event with its timestamp and which window it was (5-hour vs weekly), so I can see patterns (which days, which weeks).
  3. Surfaced in both places:
  • claude.ai → Settings → Usage as a history/chart view.
  • The /usage command in Claude Code (a --history view or similar), so CLI-heavy users don't have to leave the terminal.
  1. Optional but ideal: token/message consumption trend per window over time, and an export (CSV/JSON) so power users can analyze their own usage.

Why it matters

  • Heavy Max users currently fly blind on whether they're consistently maxing out and should adjust workflow (e.g. model choice) or consider a higher tier.
  • It turns "am I hitting limits a lot?" from a guess into data.
  • The current-window-only view makes it impossible to reason about trends or justify a plan change.

What exists today (for context)

  • /usage in Claude Code — current window only, no history.
  • claude.ai usage page — current window only.
  • No local persistence of exhaustion events in ~/.claude.

View original on GitHub ↗