CommandCodeAI / CommandCodeAI/command-code

Statsline persistente para ver uso de tokens en tiempo real

Abierto
#540 1 comentario 0 reacciones 1 asignado Ver en GitHub

@aliarain ya está trabajando en esto.

Desde el 30/6/2026.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4k
Forks
350
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.