Describe the feature or problem you'd like to solve
I'd love to have a persistent token usage indicator (context bar) visible at all times in the CLI interface
Proposed solution
I'd love to have a persistent token usage indicator (context bar) visible at all times in the CLI interface — similar to a progress bar — showing how much of the
context window is currently used and how close I am to the limit.
Currently, /context works well on demand, but having it always visible (e.g., at the bottom of the screen) would make it much easier to manage long sessions and
decide proactively when to use /compact.
Example prompts or workflows
Example prompts / workflows:
- Working on a large codebase refactor across many files — after several turns I lose track of how close I am to the context limit until it suddenly degrades.
- Long debugging sessions where I'm iterating with logs and diffs — a visible indicator would tell me when to /compact before losing coherence.
- Typical prompt: "Refactor this module, then update tests, then check the docs" — multi-step tasks that consume context fast without a visible signal.
Additional context
No response
Describe the feature or problem you'd like to solve
I'd love to have a persistent token usage indicator (context bar) visible at all times in the CLI interface
Proposed solution
I'd love to have a persistent token usage indicator (context bar) visible at all times in the CLI interface — similar to a progress bar — showing how much of the
context window is currently used and how close I am to the limit.
Currently, /context works well on demand, but having it always visible (e.g., at the bottom of the screen) would make it much easier to manage long sessions and
decide proactively when to use /compact.
Example prompts or workflows
Example prompts / workflows:
Additional context
No response