| Filename | Latest commit message | Latest commit date |
|---|---|---|
Backend POST /api/topology/set-parent already shipped; the dashboard was missing the operator surface to drive it. Adds two affordances to the SW4RM tab's selection bar (alongside the existing R3ST4RT / ST0P / ST4RT / R3BU1LD / DESTR0Y / PURG3 actions): - '⇡ M0V3 → ROOT' (bulk): promote selected agents to top-level (parent=null). Disabled when all selected are already at root or the selection includes the manager (backend refuses anyway). - '⇢ M0V3 → [pick]' (single-agent only): inline <select> dropdown + button pair. Dropdown lists every container that isn't the target nor a descendant of it (client-side BFS via the existing c.parent map). On submit POSTs form-encoded 'child=<name>&new_parent=<target>' to /api/topology/set-parent; the backend re-checks the cycle invariant and re-emits a container snapshot so the tree repaints without a reload. Both POSTs hit a single URL, so addBulkButton grew an optional 'perAgentBodyFor(name)' hook to handle the body-driven endpoint shape (vs the URL-suffix /start/<name> shape every other action uses). Lifecycle endpoints unchanged. Mauve chrome (var(--mauve)) reads as 'structural change' rather than the destructive red / amber of destroy / rebuild. closes #486 |
||
| .. | ||
| packages | ||
| .gitignore | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
hyperhive frontend
npm workspaces project for the hyperhive browser-facing assets:
packages/shared/— shared modules used by both surfaces (terminal pane, Catppuccin palette + body typography).packages/dashboard/— the hive-c0re dashboard SPA.packages/agent/— the per-container web UI (default agent page, stats, screen).
Build
npm install # one-off; uses the checked-in package-lock.json
npm run build # builds every workspace into packages/*/dist/
The Rust binaries serve packages/dashboard/dist/ and
packages/agent/dist/ via tower_http::ServeDir at runtime; the
build derivation is wired up in nix/modules/frontend.nix. Per-agent
additions are layered on top of the default agent dist via the
hyperhive.frontend.extraFiles option in agent.nix.
Why npm + esbuild
- Hermetic: dependencies vendored via the checked-in lockfile;
buildNpmPackagein nix uses it as the source-of-truth so the output is reproducible without network access at build time. - esbuild: vanilla-JS bundler, no framework runtime overhead.
Each workspace's
build.mjsis ~30 lines. - Single-PR migration: see issue #273 for the design proposal and the four-commit shape (npm scaffold → nix derivations → container plumbing → Rust cutover).