| Filename | Latest commit message | Latest commit date |
|---|---|---|
c0eb6780ec
system.md carries {{ label }}-style variables and an {% if not archetype %} block in place of the config:repo / config:archetype marker pairs, so prompt.rs drops its line filter, marker parsers and string replaces. The rendered prompt is byte for byte the old one for a custom agent, an archetype agent and an empty archetype name, with and without hive, swarm, docs and operators. hive-template now drops a block tag's own line.
|
||
| .. | ||
| 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/.