GoKawiilBackground subagents that run alongside your main session. Type /swarm to open the dashboard, then n to spawn one. Each agent is a separate zot subprocess with its own model loop, its own persistent session file, and its own chat in the dashboard — but they all run in the same working directory as the host, so they see and edit the same files you do. You keep working in your main session; the subagents work in parallel.
Agents edit the same files you do. They use the same read / write / edit / bash tools as the main agent against the host's working directory. There's no per-agent worktree or branch. If you need parallel edits on isolated checkouts, set that up yourself with git worktree outside zot.
Press enter on any row to open that agent's transcript — a chat overlay with an always-on inline composer at the bottom, streaming auto-follow, and a busy spinner showing the agent's current activity ( thinking , tool: edit_file , etc.). Type and hit enter to send a follow-up; esc returns to the dashboard.
Common shapes from the command line so scripts and headless flows work the same as the dashboard:
/swarm # open the dashboard /swarm new <task> # spawn an agent /swarm new --model gpt-5 <task> # pin the new agent to a model /swarm logs <id> # jump straight into one transcript /swarm send <id> <text> # send a follow-up without the dashboard /swarm resume # pick a stopped agent to bring back /swarm kill <id> # stop a running agent (its state stays) /swarm remove <id> # delete the agent's session and state
Agents are scoped to the session that spawned them and only show up in that session's dashboard. They persist across zot restarts under $ZOT_HOME/swarm/agents/<id>/ ; press R on a detached row to bring one back on the same session and inbox socket so the conversation continues where it left off.
Everything per-agent (session file, events log, inbox socket, meta) lives under $ZOT_HOME/swarm/agents/<id>/ . The agent's actual code edits land directly in your repo; track them with normal git status / git diff .
/session export does not bundle subagents — a .zotsession is just the main chat transcript, and a swarm agent's state (session file, unix-socket inbox) is machine-local and can't round-trip through one. To share what an agent said, copy it out of the transcript view manually.