Repository navigation
Companion fix to v3.2.0. That release pitched the dashboard UI as a current feature in its README; per `src/DEPRECATED.md` the UI was vaporware and the canonical control surface is Claude Code as orchestrator + wezbridge MCP + Telegram, not a browser dashboard. This release makes the repo + README match reality.
What changed
- Deleted `src/dashboard.html` (180KB) — was vaporware, buttons were fake
- Dropped the `GET /` handler that served it from `dashboard-server.cjs`
- Dropped the noop `POST /api/panes/:id/queue` and `/inject-context` handlers that only existed for the deprecated UI
- Deleted `docs/screenshots/dashboard.png` and removed it from the README
- Removed the HTML-marker contract test that was checking elements that no longer exist
- Rewrote README sections that pitched the dashboard UI: architecture diagram, "What it looks like", v2.5/v2.6 "What's new", Quick start step 7, roadmap
What's still alive
The dashboard daemon on port 4200 is still required — it backs the wezbridge MCP server. `mcp__wezbridge__discover_sessions` and friends fetch `/api/panes` against it. Boot it with `npm run dashboard`. It just doesn't serve a browser UI anymore.
Tests
184/184 unit tests passing.
Migration from v3.2.0
If you upgraded to v3.2.0 and bookmarked `http://localhost:4200/\` expecting a UI, that page now returns 404 — this is intentional. Use the `mcp__wezbridge__*` tools from inside any Claude Code or Codex session for control. See the updated Quick start in the README.
Full diff: v3.2.0...v3.2.1