Manage · Dashboard quickstart

Dashboard quickstart

Wire the dashboard into a fresh repo in four steps. No env-var hunt. Clone, start the server, open localhost, and you're reading your brain in a browser in under three minutes.

See it in motion

Where to find it

  • Desktop: http://localhost:4000/, then Manage → Dashboard quickstart in the sidebar.
  • Keyboard: ⌘ K, then type “Dashboard quickstart”.
  • On disk: .claude/brain/dashboard.README.md

What it does for you

Four steps, zero ambiguity.Clone repo-dashboard · npm start · open http://localhost:4000 · add your first repo from the picker (or edit the committed repos.config.json before your first boot: it only seeds the DB once, so hand-editing it after that has no effect, use the Settings UI or repo-dashboard add instead). Secrets stay in env vars.
Multi-repo from minute one.Add a second repo from the picker or with repo-dashboard add. The aggregator mirrors it as a worktree, indexes its brain, and the tier-0 picker shows both.
No bundler, no framework lock-in.Plain Node + plain HTML. npm ci finishes in seconds; the server boots straight from source with no build step. Hack any tab in plain JavaScript.

Bootstrap a brain in any tracked repo that doesn’t have one

The aggregator works on day one for security, env doctor, vulnerabilities, and settings - even with no .claude/brain/. To unlock the brain-powered tabs (Sessions, Decisions, Errors, Wiki, Roadmap, Pull requests) in a given tracked repo, open Repo bootstrap in the sidebar (Manage → Help → Repo bootstrap), copy the prompt, and paste it into Claude Code, Cursor, or Codex pointed at that repo. The LLM creates .claude/brain/, CLAUDE.md, the skills, and the CI gates. Refresh the dashboard - the brain tabs light up. Plan for 2 to 3 minutes end-to-end including the paste.

Configure

Per-repo entries in repos.config.json support ${env:VAR} substitution for any secret (telemetry tokens, GitHub PATs). Document the var in .env.example + .claude/brain/config.md so the next dev knows what to set.

Use it well

Run the dashboard locally; don't deploy it. The whole point is your brain stays on your laptop, in your repo, on disk you control. When a teammate needs the same view, they clone the same repo-dashboard and add their repos.config.json. The hosted Team SKU exists for the rollup view, not as a replacement.

Read more