Expose subscription quota/usage data in statusLine JSON

Feature Request

Problem

When using Claude Code with a Team subscription, there's no way to know how much of the included token allowance has been consumed or when it resets. The current statusLine JSON input only provides session-scoped data (cost.total_cost_usd), which doesn't reflect subscription-level usage.

This makes it difficult for users to be cost-aware and avoid unexpected overage charges.

Proposed Solution

Add subscription/quota-related fields to the statusLine JSON input, for example:

{
  "subscription": {
    "plan": "team",
    "tokens_used": 4500000,
    "tokens_included": 10000000,
    "tokens_remaining": 5500000,
    "used_percentage": 45,
    "resets_at": "2026-03-01T00:00:00Z",
    "is_overage": false
  }
}

Key fields

• tokens_remaining / used_percentage — How much of the included allowance is left
• resets_at — When the billing cycle resets
• is_overage — Whether the user has exceeded included tokens and is now on paid overage

Use Case

Users building custom statusLine scripts (via statusLine.command in settings) want to display subscription awareness directly in their terminal — e.g. a visual bar showing plan usage, a warning when approaching the cap, or a countdown to reset. Currently this is impossible without manually checking the web dashboard.

Context

The statusLine feature already exposes rich session data (model, context window, cost, duration, etc.) — this would be a natural extension to help users manage their usage proactively.