CommandCodeAI / CommandCodeAI/command-code

Statsline persistente para ver uso de tokens en tiempo real

Offen
#540 1 Kommentar 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@aliarain arbeitet bereits daran.

Seit 30.6.2026.

Vorherrschende Sprache
Keine Sprachdaten
Sterne
4k
Forks
350
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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
  1. Start a Command Code session with cmdc
  2. Work through several turns of conversation
  3. Notice there is no visible token usage indicator in the UI
  4. 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.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.