| Filename | Latest commit message | Latest commit date |
|---|---|---|
Pairs with damocles PR #566 (broker primitive + dashboard `POST /api/agent/{name}/mark-all-read` route). The agent's per-container inbox side-panel now gets a header row with a `✓ mark all read` button that: - confirms via a one-line dialog (the action is destructive: any pending broker message for this agent is acked, the harness won't receive a wake-prompt for them) - POSTs to the host dashboard (cross-origin, same pattern as the existing operator-answer flow on this page) - surfaces `{ marked: N }` in an inline status pill, then triggers a `refreshState` so any state-derived surfaces re-read fresh - stays out of the way when the inbox is empty (only renders above a non-empty rows list) Note: `recent_for` returns the most-recent-N messages regardless of ack state, so clicking does NOT visually empty the rows list. The status pill ("✓ marked N as read") is the operator-facing confirmation; the next `turn_start` will show `0 unread` in its badge. Tooltip on the button calls this out so the operator isn't surprised the row list stays put. CSS mirrors the existing answer-form button family (mauve hover on bg-elev background) so it reads as a peer affordance, with a border-bottom separating it from the message list. |
||
| .. | ||
| 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).