dashboard

1# /dashboard — Harness Observability Dashboard
2 
3## When to Use
4 
5- "What's happening?" / "Status?" / "What's going on?"
6- "Show activity" / "Show me the dashboard"
7- After returning to a project after time away
8- When /do routes "status", "dashboard", "what's happening", "what's going on", "show activity"
9- Directly: `/dashboard`
10 
11## Inputs
12 
13None required. Works with whatever state exists on disk.
14 
15## Protocol
16 
17### Step 0: RUN DASHBOARD IMPLEMENTATION
18 
19Run the local dashboard implementation from the project root:
20 
21```bash
22node scripts/dashboard.js
23```
24 
25If the package scripts are available, this equivalent command is also valid:
26 
27```bash
28npm run dashboard
29```
30 
31The script is read-only. It renders a user-facing control-plane snapshot from
32`.planning/`, telemetry, hook config, coordination state, worktrees, and cost
33data. Use the manual collection protocol below only as a fallback if the script
34is missing or fails in the current project.
35 
36### Step 1: COLLECT STATE
37 
38Read the following sources. Each is optional — if a file or directory doesn't
39exist, treat it as empty. Never crash on missing state.
40 
41**Campaigns:**
42- Glob `.planning/campaigns/*.md`
43- For each file, read the first 40 lines to extract:
44  - `Status:` field
45  - `Direction:` field (truncate to 60 chars)
46  - Phase progress (search for `Phase N of M` or `## Phase` headings)
47  - Most recent line starting with `- [` from the Decision Log
48- If all phases are complete but status is still active, report
49…