Statsline persistente para ver uso de tokens en tiempo real

Ouverte
#540 1 commentaire 0 réactions 1 personne assignée Voir sur GitHub

@aliarain y travaille déjà.

Depuis le 30/6/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

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.

Langage dominant
Aucune donnée de langage
Étoiles
4k
Forks
350
Métriques de merge des PR
Aucune PR mergée en 30 j

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de CommandCodeAI/command-code

Toutes les issues de CommandCodeAI/command-code

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.