| Filename | Latest commit message | Latest commit date |
|---|---|---|
757e6fc1a7
The agent roster page opened with how an agent comes to exist (the identity store, swarmctl, the swarm UI, the ruth archetype), which is the swarm's doing. That text now sits in a "Who is on the roster" section of the swarm page, and the roster page keeps what is a hive's and an agent's: the hive's own list, who may reach whose state, and that the manager is a normal agent. |
||
| .. | ||
| agent-roster.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 and config changes — what survives a restart, a destroy and a purge, and 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/.