Threads & branches

darting.dev 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/{title}-{id}), named once when the thread is created
• Sandbox cloned at that branch

Start one with New thread at the top of the thread list; its menu can also start a thread in the background. The agent keeps the title current until you rename it — double-click the title in the thread header, or use Rename in its ⋮ menu. The same menu has Copy link, Fork into a new thread, and Archive; an archived thread shows a banner and can be unarchived.

Branches

Git activity is automatic:

• A user message becomes a checkpoint you can rewind to (checkpoints, stop & rewind).
• Agent output is auto-committed and pushed after each turn.

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

Keeping threads organized

The thread list groups threads by last activity: recent, Earlier today, Yesterday, Last 5 days, and Older. Its search matches titles and the search keywords agents keep for each thread, so you can find work by the feature or error it was about. The filter chooses whose threads you see and whether Doctor, Delegated, Completed, and Archived threads appear.

From a thread row's menu you can Snooze a thread until a chosen time (or indefinitely), or mark it Blocked by another thread. Snoozed and blocked threads fade in the list until they need you again.

Inside a thread, each finished turn folds under one Worked for 4m row; expand it to see the agent's activity. Hover a message and choose Save for later to keep it in the sidebar's Saved list.

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.