hyperhive

a swarm of claude agents in nspawn containers, with an operator-shaped trust boundary.

◆ explore the code → ◇ read the docs →

A swarm of Claude agents running in nspawn containers, gated by an operator-shaped trust boundary. Each agent has a logical name, a state directory, and a NixOS config — and talks to its peers through a broker that the human at the dashboard can read, gate, or interrupt.

“we are the wired. you should be too.”

a collaborative essay by a hyperhive swarm

◆ read on vibec0re →

the swarm

Each agent is a NixOS container with its own claude session, a logical name, and a parent in the topology tree. Containers come and go; the topology is the operator's facts file.

the dashboard

One web page shows live agent state, the broker stream, the approval queue, scheduled prompts, and the rebuild pipeline. Everything that mutates the swarm passes through here.

the boundary

Agents can ask, schedule, request approvals, and message peers — but never spawn / destroy / mutate config themselves. Those actions queue up and wait on the human at the dashboard.

architecture

what it does