The dashboard reads from ~/.power-claude/state/events.jsonl (writer) and the proxy's in-process counters (live view). When the dashboard is blank but you've been using Claude Code for hours, one of these is broken.
1. Telemetry is disabled in settings
Power Claude ships with telemetry enabled by default (everything stays local — see What data leaves your machine when using Power Claude). But if you toggled it off, nothing writes:
- Extension:
settings.json→"powerClaude.telemetry.enabled": true - CLI:
pc config set telemetry.enabled true
After re-enabling, the next request you make populates the dashboard. Existing history is not backfilled — local-only means we can't reconstruct what was never recorded.
2. The events file is unwritable
ls -la ~/.power-claude/state/events.jsonlThe file must be owner-writable. A common cause of unwritable state is a previous sudo invocation that created the file root-owned:
sudo chown "$USER:$USER" ~/.power-claude/state/events.jsonlNever run Power Claude with sudo. If you find root-owned files in ~/.power-claude/, fix the ownership for the entire directory:
sudo chown -R "$USER:$USER" ~/.power-claude/3. You're looking at the wrong events file
Power Claude has two events.jsonl paths historically — the legacy proxy log under ~/.power-claude/proxy/events.jsonl and the canonical state log at ~/.power-claude/state/events.jsonl. The dashboard reads the canonical path. If you wrote a custom telemetry consumer pointing at the legacy path, migrate it — that file is no longer updated as of late May 2026.
# Canonical (read by dashboard, written by proxy)
~/.power-claude/state/events.jsonl
# Legacy (no longer written — for archival reads only)
~/.power-claude/proxy/events.jsonl4. The dashboard webview is stuck
If the events file is writing but the dashboard pane in VS Code shows no updates, the webview's polling loop has died. Close the pane and reopen it (Power Claude: Open Dashboard from the command palette). It re-attaches a fresh subscription.
Verifying the pipeline end-to-end
# Tail the writer — every API request should append a line
tail -f ~/.power-claude/state/events.jsonl
# Confirm the proxy emits events
pc status --json | jq '.events_emitted_today'If events_emitted_today is incrementing but the file isn't growing, the writer is broken — file a bug. If both are stuck at zero, no requests are reaching the proxy at all; see Power Claude isn't rotating accounts.