reyn agent¶
Manage persistent agents — long-lived Session instances each with their own profile, history, memory layer, and inbox.
The auto-created default agent always exists; reyn agent new creates additional named agents. See concepts/multi-agent for the model.
Synopsis¶
Subcommands: list, new, show, rm.
reyn agent list¶
Print all active (non-archived) agents (alphabetical), with last-activity timestamp and the first line of each profile's role. Archived agents are hidden from this listing. Pass --all to include archived agents, shown as <name> (archived), so you can see / recover / purge them.
NAME LAST ACTIVITY ROLE
default 2026-05-01 13:00
researcher 2026-05-01 12:55 deep technical research, prefers primary sources
writer 2026-04-30 18:20 concise long-form prose
reyn agent new <name> [--role TEXT]¶
Create a new agent under .reyn/agents/<name>/. The directory is provisioned with a profile.yaml; history.jsonl, events.jsonl, memory/, and runs/ are created on first activity.
<name> must match the agent name regex: 1–32 characters of [a-z0-9_-] starting with [a-z0-9].
The --role text is injected into the agent's LLM system prompt — keep it short and specific. To configure allowed_mcp or any other profile field, edit profile.yaml directly after creation; see profile-yaml reference.
reyn agent show <name>¶
Print profile metadata and resolved fields:
name: researcher
created_at: 2026-05-01T12:00:00+00:00
workspace: /path/to/project/.reyn/agents/researcher
role:
deep technical research, prefers primary sources
reyn agent rm <name> [--purge] [--yes]¶
Archive the agent by default (soft-delete — data preserved, not destroyed). Pass --purge for a hard-delete that permanently destroys the agent directory and all rewind history.
reyn agent rm researcher # archive (prompted)
reyn agent rm researcher --yes # archive, skip prompt
reyn agent rm researcher --purge # hard-delete (prompted, irreversible)
reyn agent rm researcher --purge --yes
The default agent cannot be removed.
Archive (default)¶
The agent's .reyn/agents/<name>/ directory is kept in place — the data is not destroyed. This is the key distinction from --purge:
- PITR generations are preserved: the WAL-derived checkpoint history survives, so the data is recoverable.
- Topology membership is preserved: no cascade fires. The agent's team/network membership is not removed.
- A tombstone marker is written recording the archival WAL seq (the WAL-window GC hinge).
- The agent is hidden from active surfaces:
reyn agent list, the TUI Agents tab, default-topology routing, and A2Acan_sendchecks all skip archived agents. It is dormant, not destroyed.
WAL-window auto-purge: when the WAL retention window advances past the archival seq, the archived agent's directory is hard-deleted automatically (the soft-delete left the rewind window — the data is no longer recoverable). At that point the topology cascade fires and removes the agent from all topologies.
Purge (--purge)¶
Immediately hard-deletes .reyn/agents/<name>/ and destroys all PITR generations. Time-travel to before the purge is intentionally unsupported. The topology cascade fires immediately (agent removed from all topologies; team topologies whose leader is purged are deleted entirely).
Use --purge when you want a clean, permanent delete and do not need the recovery window.
Workspace layout¶
Each agent owns .reyn/agents/<name>/:
| Path | Purpose |
|---|---|
profile.yaml |
name / role / created_at / allowed_mcp |
history.jsonl |
append-only conversation + agent message log |
events.jsonl |
runtime event audit log |
memory/MEMORY.md + body files |
agent-scoped memory layer |
runs/<run_id>/ |
per-workflow-spawn workspace |
See also¶
- Reference: profile-yaml
- Reference: chat CLI
- Reference: topology CLI
- Concepts: multi-agent
- Concepts: time-travel — rewind + PITR mechanics