Skip to content

Feature Request: Usage history tracking for Pro/Max subscription users #13892

Description

@paulnegz

Feature Request

Summary: Provide Pro/Max subscription users with access to their detailed token usage history, similar to what API users get via the Admin API.

Problem

Currently, subscription users (Pro/Max) have no official way to view:

  • Historical token usage across sessions
  • Cumulative usage over time (weekly/monthly/all-time)
  • Breakdown by model (Opus, Sonnet, Haiku)
  • Usage trends and patterns

Current Limitations:

  1. /cost command shows: "With your Claude Max subscription, no need to monitor cost — your subscription includes Claude Code usage."
  2. Claude Console only tracks API usage, not subscription usage
  3. claude.ai/settings/usage shows limited current-period info, no history
  4. Local JSONL files get pruned, losing historical data

Workarounds (inadequate):

  • Third-party tools like ccusage parse local files but can't recover pruned data
  • No way to get complete historical picture

Proposed Solution

Option A: API Endpoint for Subscription Users

Extend the Admin API or create a new endpoint:

GET /v1/users/me/usage_history

Returns token usage grouped by day/week/month with model breakdown.

Option B: Enhanced /usage Command

Add a Claude Code command that queries Anthropic's backend:

/usage --history        # Show all-time usage
/usage --month 2025-12  # Show specific month
/usage --export csv     # Export data

Option C: Claude.ai Dashboard Enhancement

Provide detailed usage history at claude.ai/settings/usage including:

  • Historical graphs
  • Token breakdowns
  • Export functionality

Use Cases

  1. Personal tracking - Users want to understand their usage patterns
  2. Optimization - Identify which tasks consume most tokens
  3. Planning - Decide whether to upgrade/downgrade subscription tier
  4. Transparency - Know what you're getting for your subscription cost

Related Issues

References


🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions