CommandCodeAI / CommandCodeAI/command-code

Statsline persistente para ver uso de tokens en tiempo real

Open
#540 1 comment 0 reactions 1 assignee View on GitHub

@aliarain is already working on this.

Since Jun 30, 2026.

Dominant language
No language data
Stars
4k
Forks
350
PR merge metrics
No merged PRs in 30d

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.