[FEATURE] Add 5-Hour and Weekly Usage cap data to Statusline inputs

Resolved 💬 3 comments Opened Dec 13, 2025 by NiloCK Closed Dec 16, 2025

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

See https://code.claude.com/docs/en/statusline

CC statusline can be constructed using CC runtime data:

``` injected data
{
"hook_event_name": "Status",
"session_id": "abc123...",
"transcript_path": "/path/to/transcript.json",
"cwd": "/current/working/directory",
"model": {
"id": "claude-opus-4-1",
"display_name": "Opus"
},
"workspace": {
"current_dir": "/current/working/directory",
"project_dir": "/original/project/directory"
},
"version": "1.0.80",
"output_style": {
"name": "default"
},
"cost": {
"total_cost_usd": 0.01234,
"total_duration_ms": 45000,
"total_api_duration_ms": 2300,
"total_lines_added": 156,
"total_lines_removed": 23
},
"context_window": {
"total_input_tokens": 15234,
"total_output_tokens": 4521,
"context_window_size": 200000
}
}


But `cost` is a bit opaque for subscription accounts (Pro, Max) that have time-scoped metered usage.



### Proposed Solution

Add `usage` field to the json inputs here:

"usage": {
"current_session": 0.4525 // eg - 45.25 percent
"resets_at": utcTimeStamp || localeString
}


### Alternative Solutions

_No response_

### Priority

Medium - Would be very helpful

### Feature Category

Configuration and settings

### Use Case Example

_No response_

### Additional Context

_No response_

View original on GitHub ↗

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