[FEATURE] Expose Plan Quota/Usage Data to StatusLine

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

Summary

Add account-level quota and usage data to the JSON input passed to statusLine scripts, enabling users to monitor their plan limits (daily/monthly usage percentages, remaining credits, reset times) directly in the status line.

# Current Situation

The statusLine currently receives session-level data (context window usage, session cost, token counts) but lacks account-level quota information. Users must repeatedly use /usage or /cost commands to check their plan usage, creating
unnecessary friction.

Problem

• No visibility into daily/monthly quota consumption without manual commands
• Can't see percentage of plan limits used (e.g., "30% of daily credits used")
• No indication of when quotas reset
• Difficult to pace usage throughout the day/month

# Proposed Solution

Extend the statusLine JSON input to include plan-level usage data:

{
"plan": {
"tier": "pro", // or "max", "free", etc.
"quota": {
"daily_limit_usd": 10.00,
"daily_used_usd": 3.50,
"daily_used_percentage": 35,
"daily_remaining_usd": 6.50,
"daily_reset_time": "2026-02-18T00:00:00Z",

"monthly_limit_usd": 300.00,
"monthly_used_usd": 45.20,
"monthly_used_percentage": 15,
"monthly_remaining_usd": 254.80,
"monthly_reset_time": "2026-03-01T00:00:00Z"
},
"rate_limits": {
"requests_per_minute": 50,
"requests_remaining": 45,
"reset_time": "2026-02-17T14:35:00Z"
}
}
}

# Benefits

1. Reduced friction - At-a-glance quota monitoring without interrupting workflow
2. Better usage awareness - Users can pace their usage throughout the day/month
3. Proactive planning - See reset times to plan intensive work sessions
4. Prevent surprises - Know when approaching limits before hitting them
5. Customizable display - Users can choose which metrics matter most to them

## Example Use Cases

### Status line showing daily usage:

> Sonnet 4.5 | $0.0234 | 15m 32s | Context: 12% | Daily: 35% ($3.50/$10.00) | Resets in 9h 25m

### Status line for heavy users:

> Opus 4.6 | $2.45 | 1h 20m | Monthly: 67% ⚠️ | Daily: 85% 🔴 | Reset: 2h 15m

### Minimalist version:

> Sonnet | Context: 8% | Quota: 35% 🟢

## Technical Considerations

• Data should be fetched/cached efficiently to avoid API overhead
• Update frequency could be configurable (e.g., every N requests, every M minutes)
• Privacy-conscious users might want to opt-out via settings
• Graceful degradation if quota data unavailable

Proposed Solution

Extend the statusLine JSON input to include plan-level usage data:

{
"plan": {
"tier": "pro", // or "max", "free", etc.
"quota": {
"daily_limit_usd": 10.00,
"daily_used_usd": 3.50,
"daily_used_percentage": 35,
"daily_remaining_usd": 6.50,
"daily_reset_time": "2026-02-18T00:00:00Z",

"monthly_limit_usd": 300.00,
"monthly_used_usd": 45.20,
"monthly_used_percentage": 15,
"monthly_remaining_usd": 254.80,
"monthly_reset_time": "2026-03-01T00:00:00Z"
},
"rate_limits": {
"requests_per_minute": 50,
"requests_remaining": 45,
"reset_time": "2026-02-17T14:35:00Z"
}
}
}

Alternative Solutions

Alternatives Considered

1. Using /cost command - Current workaround, but creates friction
2. External API integration - Users could fetch quota data separately, but requires API keys and extra complexity
3. Web dashboard only - Doesn't provide in-CLI visibility

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_