[FEATURE] Official usage analytics dashboard for Max Plan subscribers

Resolved 💬 4 comments Opened Feb 22, 2026 by Seungwoo321 Closed Mar 23, 2026

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

Claude Code currently only shows weekly usage limits with no historical data or trends.
As a Max Plan subscriber paying $330/month (two accounts), I need better visibility into my usage.

Current limitations:

  • No historical usage patterns (daily/weekly/monthly trends)
  • No breakdown by model, project, or session
  • No predictive insights (when will I hit my limit?)
  • No cost analysis or token consumption details

Current Workaround

Many users rely on third-party tools like ccusage (10k+ GitHub stars) to analyze local JSONL files. While helpful, paying customers shouldn't need external tools for basic usage visibility.

Proposed Solution

An official dashboard (web or CLI) providing:

  1. Usage graphs - Daily/weekly/monthly token consumption trends
  2. Model breakdown - Cost analysis by Opus, Sonnet, Haiku
  3. Project analytics - Per-project/session usage breakdown
  4. Alerts - Notifications before hitting limits (e.g., 80% warning)
  5. Comparison (optional) - Anonymous benchmarks with similar users

Priority

Medium - Important for paying customers

Feature Category

Usage reporting / Analytics

Use Case Example

As a Max Plan subscriber, I want to:

  1. See my usage trend over the past month
  2. Understand which projects consume the most tokens
  3. Get notified before hitting weekly limits
  4. Make informed decisions about plan optimization

Additional Context

Related but different from:

  • #26394 (multi-instance monitoring) - This request focuses on account-level usage analytics and historical data
  • #18550 (cost tracking) - This request is about visual dashboard and trends, not just raw tracking

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗