CommandCodeAI / CommandCodeAI/desktop

[Bug]: usage/credits indicator missing in bottom-left + /usage does nothing

Open
#70 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Shell
Stars
80
Forks
2
PR merge metrics
No merged PRs in 30d

Description

GUI version

0.1.30

Operating system

Windows

Reproduction steps
  1. Open the Command Code desktop app (0.1.30, Windows).
  2. Look at the bottom-left corner of the sidebar -> the credits/usage indicator that used to be there is gone.
  3. Type /usage in the chat input and press Enter -> nothing happens: no overlay, no output, no error message.
    Reproduces 100% of the time.
Expected behavior

The bottom-left credits/usage indicator should be visible again, and /usage should display credits, plan, and usage metrics (per the slash-command reference).

Actual behavior
  1. The credits/usage indicator that used to sit in the bottom-left corner is no longer shown.
  2. Typing /usage in the chat input does nothing at all.

This is not an account, billing or login problem. %APPDATA%\Command Code\app-state.json contains a fresh, successful account fetch:

  • accountCache.result.success = true
  • accountCache.fetchedAt = 2026-09-17T01:15:54+08:00
  • overview contains user, identity, credits, subscription, usage, windowLimits
  • subscription.status = "active", subscription.planId = "individual-goat"
  • credits.monthlyCredits is populated; windowLimits.fiveHour and .weekly are populated

It is not a setting I can turn back on either:

  • "cmdc config list" (the full settings registry) has no key for a usage/credits display.
  • %APPDATA%\Command Code\app-state.json has no related toggle (appState = threads / model / permissionMode / projects / ..., nothing usage-related).

I also confirmed 0.1.30 is the newest release of this repo (published 2026-09-16), so there is nothing to update to.

Screenshots, recordings, or sanitized logs

No response

Safety check
  • I removed credentials and private project information from this report.

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.

Research direction

Start by tracing the /usage slash-command entry point and the bottom-left sidebar usage indicator in the desktop app. Use %APPDATA%\Command Code\app-state.json and its accountCache overview as confirmation that account, credits, subscription, and usage data are available. Done means /usage responds with the expected metrics and the credits/usage indicator is visible again on Windows.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.