Feature request: Configurable status line with color-coded token/context usage
Resolved 💬 3 comments Opened Mar 8, 2026 by Kn8ofn8s Closed Mar 11, 2026
Feature Request
Problem
During long Claude Code sessions, there is no persistent, at-a-glance way to monitor context window usage or token consumption. The only options are:
/cost— requires manual invocation, interrupts flow- Per-response token info — transient, easy to miss
- Context compression notifications — only fires when already near the limit
For users working on large codebases with extended sessions, it would be valuable to have continuous visibility into how much context remains before compression kicks in.
Proposed Solution
A configurable status line (persistent bar at the bottom of the terminal, similar to vim/tmux status bars) that could display:
- Context window fill percentage — color-coded (green/yellow/red) based on remaining capacity
- Token usage — cumulative input/output tokens for the session
- Session cost — running cost estimate
- Current model — which model is active (Opus/Sonnet/Haiku)
Configuration
Ideally configurable via ~/.claude/settings.json or a dedicated config, allowing users to:
- Enable/disable the status line
- Choose which metrics to display
- Set color thresholds (e.g., yellow at 60% context usage, red at 85%)
Why This Matters
- Helps users make informed decisions about when to start a new session vs. continuing
- Reduces surprise context compressions mid-task
- Provides cost awareness without interrupting workflow
- Particularly useful for complex multi-file tasks where context fills quickly
Alternatives Considered
- External terminal multiplexer status bars polling log files — fragile, requires extra setup
- Periodic
/costchecks — disruptive to workflow
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗