Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/docs/2-handbook/agents
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-11-07 12:28:44 +01:00
..
agent-roster.md docs: the handbook follows the three layers: swarm, hives, agents 2026-11-07 12:19:36 +01:00
config-changes.md swarm: a deploy goes out only once its closure is cached and the hive has its cache facts 2026-11-07 12:28:44 +01:00
persistence.md docs: the handbook follows the three layers: swarm, hives, agents 2026-11-07 12:19:36 +01:00
README.md docs: the handbook follows the three layers: swarm, hives, agents 2026-11-07 12:19:36 +01:00
security.md docs: the handbook follows the three layers: swarm, hives, agents 2026-11-07 12:19:36 +01:00
web-page.md docs: the handbook follows the three layers: swarm, hives, agents 2026-11-07 12:19:36 +01:00

Agents

An agent is one Claude instance in its own NixOS container, with its own state directory, forge account and matrix accounts. This section covers running one: its identity, what survives a restart, how its config changes, what its own page shows and how far you can trust it.

  • Roster — the agents of a hive, and who may do what to whom.
  • Persistence — what survives a restart, a destroy and a purge.
  • Config changes — how a change to an agent's config flows from a pull request to its container.
  • The agent's web page — the per-agent terminal view, its actions and its endpoints.
  • Security model — the trust model, the prompt-injection threat model and credential isolation.

The swarm creates and configures agents: the create form and its archetypes are in swarm/archetypes.md, logging an agent in to claude is in swarm/claude-login.md, and you set an agent's permissions with swarmctl agent permissions or on the swarm UI. What an agent can do inside its container is in 4-implementation/agent-tools/.