| Filename | Latest commit message | Latest commit date |
|---|---|---|
e5c55257f8
the harness writes the reason into the pause marker when it pauses itself and reports it as paused_by_hive in its turn-state header. swarm-controller declares such an agent paused (only if declared up) and shows the reason on the agents status row and the swarm ui card. |
||
| .. | ||
| agent-roster.md | ||
| config-changes.md | ||
| persistence.md | ||
| README.md | ||
| security.md | ||
| web-page.md | ||
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/.