Threads & branches

Agent Swarm maps cleanly onto git: a project is a repo, and a thread is a branch.

Threads

A thread is one conversation with a lead agent. A project can have many threads, each with its own:

• Conversation log and execution history
• Git branch (agent-swarm/{agentId})
• Sandbox cloned at that branch

Threads are numbered by creation order — Thread 1 is the first created — so they stay stable as you open and close them. Start a new one any time with + New Thread, optionally cloning an existing thread's rules and context.

Branches

Git activity is automatic:

• A user message becomes a checkpoint commit.
• Agent output is auto-committed and pushed.
• Automations branch from their parent and merge back when they finish.

# each thread works on its own branch
git checkout -b agent-swarm/3f2a   # Thread 2
# ... agent commits land here, never on main

The branch graph

The Git tab renders an SVG graph of every branch:

• The default branch is the trunk; threads and automations fan out into their own lanes.
• Each commit is clickable — see its diff, message, timestamp, and +/- summary inline.
• Status badges show whether a branch has unique commits, is merged, or hit a conflict.

Because each thread is just a branch, running five things at once is no different from running one — they simply live in parallel lanes until you decide to merge.