Feature Request: Add token usage/context budget to status line JSON input
Resolved 💬 3 comments Opened Nov 14, 2025 by SmithLabsLLC Closed Nov 18, 2025
Feature Request
Summary
Add token usage and remaining context information to the JSON input provided to status line scripts.
Current Behavior
The status line JSON input currently includes:
- Model information (id, display_name)
- Working directory (current_dir, project_dir)
- Cost metrics (total_cost_usd, duration, lines added/removed)
- Session details
Requested Feature
Add fields for:
- Current token usage - Total tokens used in the current session
- Remaining context - Tokens remaining until auto-compact
- Context limit - Maximum context window for the current model
- Token budget - Percentage of context used
Use Case
Users want to monitor their context usage in real-time via the status line to:
- Know when they are approaching auto-compact
- Manage their conversation context more effectively
- Make informed decisions about when to start a new session
Suggested JSON Fields
Workaround
Currently, token information is only available through OpenTelemetry metrics export, which requires external monitoring infrastructure and is not suitable for real-time status line display.
Related
This would complement the existing cost tracking features and provide users with better visibility into their session state.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗