CommandCodeAI / CommandCodeAI/command-code
Statsline persistente para ver uso de tokens en tiempo real
@aliarain ci sta già lavorando.
Dal 30/6/2026.
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 4k
- Fork
- 350
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Summary
Add a persistent statsline showing real-time token usage in the terminal UI, similar to Claude Code's statsline. Currently the only way to check token usage is by running /usage or /context commands, which interrupts the workflow.
Expected Behavior
A persistent statsline (e.g., at the bottom or top of the terminal) that displays real-time token usage metrics such as input tokens, output tokens, total tokens, and optionally cost/credits consumed during the current session—updated automatically without requiring any command.
Actual Behavior
There is no persistent token usage indicator in the terminal UI. The user must manually run /usage or /context every time they want to check their token consumption, which is disruptive and makes it hard to keep track of usage during long sessions.
Steps to reproduce the issue
- Start a Command Code session with cmdc
- Work through several turns of conversation
- Notice there is no visible token usage indicator in the UI
- Run /usage to check usage — confirms it works but requires manual action each time
Command Code Version
0.40.14
Operating System
Windows
Terminal/IDE
Unknown
Shell
cmd.exe
Additional context
Claude Code shows a statsline at the bottom of the terminal with input/output token counts that updates after each response. This is very useful for monitoring usage without breaking flow. A similar feature in Command Code would greatly improve the developer experience, especially during long coding sessions where token consumption adds up quickly. Even a minimal version showing just total tokens for the current session would be valuable.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.