| Filename | Latest commit message | Latest commit date |
|---|---|---|
Replaces AgentsPage's Table-rendered roster with one AgentCard per agent: name/status/wanted on the first line, the free-form status message on the second (mara, scoping #4257: "main view: name, status, message, wanted" / "message as second line" / "more like card per agent"). Everything the old table's other columns carried (hive, matrix link-account, config-PR link, destroy) moves into a detail panel that opens on card click, reusing the existing Dialog modal rather than a new docked/slideover primitive - the shared hive-side-panel drawer is a shadow-DOM custom element swarm-ui's esbuild config can't consume yet (same gap Dialog.tsx's own comment already flags for hive-dialog). WantedMenu gains a showDestroy flag: the card's own menu keeps the three everyday states, destroy gets its own button in the detail panel instead of a fourth dropdown entry next to states someone reaches for often. Known regression, flagged for follow-up rather than silently dropped: the old table's per-column sort/filter has no replacement in this view yet. Backend list/detail endpoint split (also requested in #4257) is deliberately left for a follow-up PR - it's an orthogonal optimization, not required for this interaction to work correctly against the existing single /api/agents/status response. |
||
| .. | ||
| packages | ||
| .gitignore | ||
| npm-deps-hash | ||
| 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/packages/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 the tracked design proposal and the four-commit shape (npm scaffold → nix derivations → container plumbing → Rust cutover).