Troubleshooting
Status line not showing
Section titled “Status line not showing”- Check if the plugin is installed by running
/plugin listin Claude Code. - Verify that
~/.claude/settings.jsoncontains astatusLineentry pointing atplugins/data/claude-dashboard-claude-dashboard/statusline.mjs. - If it’s still not showing, try restarting Claude Code.
If the status line still does not appear after restarting, try running /claude-dashboard:setup again to regenerate the configuration.
Rate limits showing warning
Section titled “Rate limits showing warning”If rate limit widgets display a warning icon instead of percentages:
- Expired token: Your API token may have expired. Re-login to Claude Code to refresh it.
- Network issue: Check your internet connection.
- API rate limited: The dashboard caches API responses for 60 seconds. Wait for the cache to refresh and try again.
Wrong language
Section titled “Wrong language”If the status line is showing the wrong language, run the setup command with an explicit language argument:
/claude-dashboard:setup normal en # Set to English/claude-dashboard:setup normal ko # Set to KoreanYou can also edit the configuration file directly at ~/.claude/claude-dashboard.local.json and change the "language" field to "en", "ko", or "auto".
Cache issues
Section titled “Cache issues”API response cache is stored in ~/.cache/claude-dashboard/. If you are experiencing stale data or unexpected behavior, clear the cache:
rm -rf ~/.cache/claude-dashboard/Cache files are automatically cleaned up after 1 hour, so this is typically only needed when debugging issues.
Status line not updating after a plugin update
Section titled “Status line not updating after a plugin update”Normally nothing to do here: statusLine points at a permanent shim path
(plugins/data/claude-dashboard-claude-dashboard/statusline.mjs) that resolves the newest
installed build on every render, so /plugin update alone is enough.
If the status line still shows the old version, restart Claude Code once — a SessionStart
hook installs the shim and migrates settings.json automatically, and it only needs to run
once. If it persists after restarting, run /claude-dashboard:update to repair it manually
(this is also the fix if you have hooks disabled):
/claude-dashboard:updateThe first time this migration runs, it writes a one-time settings.json.bak backup next to
settings.json, which you can use to restore the pre-migration value if you ever need to.
Because the shim always resolves the newest installed build, installing an older version has
no effect while a newer version’s cache directory still exists. To deliberately test an older
build, remove the newer version’s directory under plugins/cache/claude-dashboard/claude-dashboard/.
Multi-CLI widgets not appearing
Section titled “Multi-CLI widgets not appearing”The multi-CLI widgets (codexUsage, geminiUsage, antigravityUsage, zaiUsage) auto-hide when their respective CLIs are not detected:
- codexUsage: Requires
~/.codex/auth.jsonto exist - geminiUsage / geminiUsageAll: Requires
~/.gemini/oauth_creds.jsonto exist - antigravityUsage / antigravityUsageAll: Requires
~/.gemini/antigravity-cli/antigravity-oauth-tokento exist - zaiUsage: Requires detection via
ANTHROPIC_BASE_URLenvironment variable
Make sure the corresponding CLI is installed and authenticated before expecting these widgets to appear.