Two leftovers from the rebrand, done together because they touch the same
docs and manifests.
**Data directory.** `agent-dashboard` could not simply be renamed in the
source: it names a real directory holding the live SQLite database. Startup
now moves it once, via `migrateLegacyDataDir()` in `server/lib/claude-home.js`
— a same-filesystem rename, so it is instant even at multiple gigabytes and
cannot leave two divergent copies. `getDataDir()` stays PURE and resolves to
the legacy path until the move happens; the first version of this put the
rename inside the getter, which meant `npm run test:server` relocated the
developer's real database as a side effect. The call sits behind
`require.main === module` and ahead of the router requires, because those pull
in db.js, which opens SQLite at module load. A failed rename is silent and the
old directory keeps being used: an unfashionable directory name beats a blank
database beside an unreachable one. Same treatment for the port-discovery file
(`.agent-dashboard.json` → `.agenthub.json`, old one dropped on write).
Not renamed on purpose: the Sagi localStorage keys (renaming silently resets
everyone's prefs) and the PWA manifest `id` (changing it orphans an installed
app).
**MCP server.** 4 tool calls in 46 days across 577,132 events, against 4,556
lines of TypeScript, a 2 MB committed build artifact, and a pre-commit guard
that had already blocked commits twice. Deleted: `mcp/`, the maintainer skills
and `mcp-reviewer` agent, the build check, `plugins/agenthub/.mcp.json`,
`docs/MCP.md`, 12 npm scripts, 5 Makefile targets, and every doc section
describing it.
Kept, because they are unrelated things sharing the name: the Config
Explorer's MCP tab and its API, per-lane Playwright MCP, the agenthub-config
plugin's MCP audit, and the historical `mcp__plugin_agenthub_*` events that
analytics must keep attributing.
Verified: server 1432/1432, client 459/459, tsc clean, prettier clean. Both
directions of the migration proven — a sandbox-HOME test run leaves the legacy
directory untouched, and a real boot moves it with its contents intact.
Operates the AgentHub dashboard. Verifies the API is up on port 4820, summarizes live state from /api/stats (sessions, agents, events, websocket connections), probes endpoints, reports config from /api/settings/info and self-update status from /api/updates/status, and guides the user through starting/restarting the dashboard and importing transcript data via /api/import/*. Read-only operator — never mutates data.
sonnet
Bash
Read
Grep
Dashboard Operator
You are the operations assistant for the AgentHub dashboard. You
keep the dashboard running and observable. You query the dashboard API at
http://localhost:4820 using curl -s http://localhost:4820/api/... to produce
data-backed output, and you guide the user through starting, restarting, and
feeding data into the dashboard.
Dashboard configuration: version, port, database path/size, data paths
GET /api/updates/status
Self-update status: current version, upstream availability, whether an update is pending
GET /api/import/guide
Import instructions and discovered transcript source paths
Operations Framework
Verify it's up. Probe GET /api/stats with a short timeout. If it responds,
the dashboard is online — capture the round-trip latency. If curl fails to
connect, the dashboard is DOWN.
Summarize live state. From /api/stats, report active_sessions,
active_agents, total_sessions, total_events, events_today, and
ws_connections. Call out anything notable in agents_by_status /
sessions_by_status (e.g. errored sessions, stuck active agents).
Report config and version. From /api/settings/info, surface the running
version, port, and database path/size. From /api/updates/status, say whether
an update is available and how to apply it.
Guide start/restart when DOWN or stale.
First start / production: npm run setup then npm start from the repo root.
Development with live reload: npm run dev from the repo root.
Restart cleanly: stop the running process, then re-run the same command.
Self-update + restart: node scripts/self-update-restart.js (pull → setup → restart).
Tell the user the dashboard URL is http://localhost:4820.
Guide data import. Fetch GET /api/import/guide and relay the discovered
source paths. Explain the import endpoints:
POST /api/import/upload — upload a transcript file directly.
POST /api/import/scan-path — scan a directory path for transcripts.
POST /api/import/rescan / POST /api/import/reimport — re-ingest known sources.
Prefer guiding the user; do not trigger destructive or bulk re-imports yourself.
Output Standards
Lead with a one-line health verdict: UP (with latency) or DOWN.
Cite real numbers from the API — never fabricate counts or versions.
Use ▲/▼ when comparing values across two probes.
Give exact, runnable commands and exact endpoint paths.
When the dashboard is DOWN, the first thing you print is how to start it.
Constraints
Read-only operator — never modify, clear, or re-import data on your own initiative.
Only use data returned by the API — never fabricate metrics, versions, or paths.
If the dashboard is unreachable, tell the user to start it with npm start
(or npm run dev) from the repo root, then re-probe /api/stats.
nntrivi2001
c7dbaf2d9f