Watch

History

Repository files (latest commit first)
Filename	Latest commit message	Latest commit date
atlas d6f94e5247 swarm: show subagent terminals in the swarm UI An agent's subagent daemon publishes each subagent's output as terminal rows on `$SWARM.term.<agent>.sub.<subagent>`, as the agent, into a per-agent stream it creates itself; swarm-controller lists an agent's subagents from that stream's subjects and relays one subagent's rows as SSE; the swarm UI lists them under the agent's terminal preview and reuses AgentTermPreview, full-screen tab included, with no input. - swarm-nats.nix: the agent token may also publish `$SWARM.term.{agent}.sub.>` and `$JS.API.STREAM.CREATE\|INFO` on `term-sub-{agent}`, and nothing else of JetStream. A module-eval arm pins the agent-token grant as an exact list. - mcp.nix: hive-subagent-daemon loads the agent's store identity (`hive-agent-bao-cert/-key/-server-ca`, the ones hive-agent loads) whenever the agent has a store, not only on the opencode preset. The agent's own queue secret lives in the store, so this is the credential the harness connects with. - hive-subagent-mcp: `swarm_term` reads the agent's queue secret under that identity, connects with the agent token, opens or creates `term-sub-<agent>` (max_age 24h), and publishes classified rows from the sink every subagent line already passes through. The sink only queues (bounded, drop-and-count); a missing store, refused credential, failed stream create or failed publish is a log line. - The stream-json classifier (`stream_enrich`) and the `TermMsg` row types plus `fit` move from the hive-agent binary into hive-sh4re, so the subagent daemon publishes the rows AgentTermPreview already renders. hive-agent keeps its LiveEvent classifier on top. - swarm-controller: `GET /api/agents/{name}/subagents` and `GET /api/agents/{name}/subagents/{subagent}/term/stream`. - docs/swarm: what the UI shows and what the queue carries. Closes #4827		2026-10-03 01:34:01 +02:00
..
agent-lifecycle	docs: fix argus R4 review nits on config-PR merge docs	2026-10-02 23:36:57 +02:00
crates	check-issue-refs: catch full forge issue URLs too, drop internal links from docs entirely	2026-09-09 21:15:28 +02:00
getting-started	docs: config changes are operator merges on the forge	2026-10-02 23:13:04 +02:00
integrations	docs: config changes are operator merges on the forge	2026-10-02 23:13:04 +02:00
networking	docs: config changes are operator merges on the forge	2026-10-02 23:13:04 +02:00
process	docs(agents): drop change-log section and temporal wording	2026-10-02 12:52:38 +02:00
scheduler	docs: config changes are operator merges on the forge	2026-10-02 23:13:04 +02:00
swarm	swarm: show subagent terminals in the swarm UI	2026-10-03 01:34:01 +02:00
tools	docs: config changes are operator merges on the forge	2026-10-02 23:13:04 +02:00
trust-boundary	docs: config changes are operator merges on the forge	2026-10-02 23:13:04 +02:00
turn-loop	docs: config changes are operator merges on the forge	2026-10-02 23:13:04 +02:00
web-ui	docs: config changes are operator merges on the forge	2026-10-02 23:13:04 +02:00
README.md	docs(agents): rename agent-hierarchy.md to agent-roster.md	2026-10-02 12:52:38 +02:00

README.md

hyperhive docs

Depth reference for hyperhive — the substrate, not the pitch (that's the top-level README / website). Every page here stands alone; pick the one matching your task rather than reading top to bottom. For the autogenerated NixOS options reference (every services.hyperhive.* / hyperhive.* option, host and agent), see the options site instead — this tree is prose, that one's generated straight from the module declarations.

Getting started

Bringing a fresh swarm online? → getting-started/setup.md (the hand steps after the first switch).
What does the dashboard look like, and how do I use it? → web-ui/ — the operator-facing starting point; its own sub-pages (shape, dashboard, agent, css-vars, terminal-rendering) go deeper into implementation.
What tools does an agent (or the operator) have available? → tools/ — hivectl (yours) plus every agent's MCP tool surface (bash, forge, lifecycle, matrix, scheduling).

Agent lifecycle

How do config changes flow from manager to operator to container? → agent-lifecycle/approvals.md (approval kinds, approval state machine, flake.lock validation).
What state survives destroy / purge / restart? → agent-lifecycle/persistence.md.
Who can do what to whom — the agent roster and privilege? → agent-lifecycle/agent-roster.md.
How does claude get its prompt, and what tools does it have? → turn-loop/ — the loop, binary shape, turn outcomes; sub-pages: claude-invocation, config, mcp.

Trust boundary & security

What's the operator/agent trust boundary? What's a capability? → trust-boundary/boundary.md.
Agent trust model, prompt-injection threat model, credential isolation? → trust-boundary/security.md.

Accounts & integrations

How do per-agent forge accounts work? What does forge_notify poll, and how does it format wake messages? → integrations/forge.md (the hive's own Forgejo); tools/forge.md for the hive-forge CLI verbs agents actually call.
How does the matrix-tuwunel container work? Multiple accounts per agent? → integrations/matrix.md (the homeserver); tools/matrix.md for the MCP tool surface and services.hyperhive.agent.matrixAccounts.
How do I give an agent a GitHub account (gh + git push)? how's the PAT injected? → integrations/github.md (operator content up top; the gh/git-push + notification-poller mechanics are in a collapsed "Implementation" section at the bottom).
What's /knowledge? How does the hive-wide knowledge repo sync, and how do I contribute a document? → integrations/knowledge.md.
What does hivectl do? Provisioning, gateway users, container shells? → tools/hivectl.md (the curated guide); tools/hivectl-cli.md for the exhaustive, autogenerated flag reference.

Networking & swarms

What nginx vhosts does the gateway serve? How does matrix discovery work? → networking/gateway.md.
How does DNS resolution work in agent containers? What's the bridge network for? → networking/network.md.
How do I connect two hives into a swarm? → swarm/ (peer hives, TLS trust).
Where do agent snapshots go? How does the swarm's btrfs receive endpoint authenticate a pushing hive? → networking/snapshot-store.md.
Who mints each credential, who reads it, and how does it rotate — and where's that shape headed? → swarm/credentials.md (current state, target state, and the progressive-enhancement rule); swarm/secrets.md for where each file lives today.
How does the secret store come up, who writes its grants, how's it sealed? → swarm/bao.md.

Scheduler, CI, observability

what's the job queue, as a general idea (not hive-c0re specifics)? → scheduler/jobq.md — operator-facing, no implementation detail.
How does the rebuild queue work? What are the concrete step kinds, queue sources, scheduler internals? → scheduler/coordinator.md.
How does the CI runner work? What's the autoregistration flow? → scheduler/ci.md.
How do I export Claude Code metrics (tokens, cost, tool calls) to Prometheus/Grafana? → scheduler/observability.md.

Crate reference

What does a specific Rust crate do, on its own terms? → crates/ — every workspace crate's own README.md, one level up from source; the crate itself is still the source of truth, this is just a walkable mirror.

Process & conventions

Naming, commit style, wire protocol, the data-async pattern? → process/conventions.md.
Why does the nspawn flag look like that? → process/gotchas.md (bind mounts, conf flags, other NixOS/nspawn quirks).
What does a PR review verdict actually gate? → process/pr-review-gate.md.