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

Beginne damit, den Einstiegspunkt des Slash-Befehls /usage und den Nutzungsindikator in der unteren linken Seitenleiste der Desktop-App nachzuverfolgen. Verwende %APPDATA%\Command Code\app-state.json und dessen accountCache-Übersicht als Bestätigung dafür, dass Konto-, Credit-, Abonnement- und Nutzungsdaten verfügbar sind. Als erledigt gilt die Aufgabe, wenn /usage mit den erwarteten Metriken antwortet und der Credit-/Nutzungsindikator unter Windows wieder sichtbar ist.

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.