nntrivi2001
c7dbaf2d9f
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.
Dev Container (optional)
A ready-to-use, opt-in development environment for AgentHub.
It is used only when you explicitly choose it — it changes nothing about
host-based development (npm run dev / npm start still work exactly as before).
When to use it
Use it if you want a consistent, batteries-included toolchain without installing Node, build tools, or Python on your machine — or if you're on a GitHub Codespace.
How to open it
- VS Code: install the Dev Containers extension, then run "Dev Containers: Reopen in Container" (Command Palette).
- GitHub Codespaces: Code → Create codespace on this branch.
The first build runs .devcontainer/post-create.sh, which installs all workspace
dependencies (npm run setup).
What's inside
| Component | Detail |
|---|---|
| Base image | mcr.microsoft.com/devcontainers/javascript-node:22 (matches prod) |
| Native toolchain | build-essential + python3 so better-sqlite3 compiles |
| Python | python3 / python for statusline.py and helper scripts |
| sqlite3 CLI | inspect the dashboard DB during development |
| Features | GitHub CLI, Docker-in-Docker (build/run the project's own Dockerfile) |
| Forwarded ports | 4820 (server API + WebSocket), 5173 (Vite client) |
| Editor | ESLint + Prettier (format on save), Vitest, Docker, YAML, Tailwind |
Everyday commands
npm run dev # server on :4820 + Vite client on :5173
npm start # production-style server (serves client/dist)
npm run test:server # node --test
npm run test:client # vitest
npm run openapi:yaml # regenerate openapi.yaml from the live spec
Claude Code hooks are HOST-side (important — issue #193)
Claude Code runs on your host, so its hooks must point at a handler path that exists on the host. This container therefore:
- does not bind-mount
~/.claude, and - does not install hooks —
scripts/install-hooks.jsrefuses to run inside a container (it would write a container-internal handler path into your host settings and break every host hook withMODULE_NOT_FOUND).
Install hooks on your host instead:
npm run install-hooks # on the HOST
The host hook handler POSTs to http://localhost:4820, which this container
forwards — so a host-installed hook reaches the containerized dashboard.
Escape hatch: if you genuinely run Claude Code inside this same container, set
AGENTHUB_ALLOW_CONTAINER_HOOKS=1beforenpm run install-hooks.
Not supported in the container
Electron desktop builds (npm run desktop:*) need a host with a display and are
host-only.