| Filename | Latest commit message | Latest commit date |
|---|---|---|
All 19 remaining cookies in app.js were attribution refs to closed issues / PRs / past mara/argus reviews. Substance is already in docs from earlier batches (PR #780). This batch collapses the cookie attributions to brief inline notes pointing at docs where appropriate. - #360 side-panel duplication note → drop closed-issue framing - #394 vibec0re header redesign (×5) → drop cookies, prose stays - #589 hive-qualified label glyphic-title note → drop cookie - #576/#542/#584 logout chain rationale → drop cookies, prose preserved (the WHY + .credentials.json + mcp-needs-auth- cache.json detail stays inline) - #14 relative paths convention → docs/web-ui.md::Per-agent relative paths pointer - #233 marked autolinks new-tab → drop cookie - #559/#566 mark-all-read flyout (×3) → docs/web-ui.md::Per-agent page (Loose-ends flyout) pointer + drop attribution - #666 ask→operator inline-answer slot (×2) → docs/web-ui.md:: Per-agent page (Ask → operator inline-answer binding) pointer app.js: 19 → 0 cookies (100% reduction). Combined with PR #780 + batch 1 + 2, app.js is fully migrated for #713 scope. Closes #713 — all agent UI files (app.js, agent.css, screen.html, index.html, stats.js, stats.html) at 0 issue-ref cookies. |
||
| .. | ||
| 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).