Git worktrees
How ForgeDeck uses git worktrees to isolate each task's agent.
Embed
<a href="https://docs.forgedeck.net/worktrees"><img src="https://docs.forgedeck.net/_api/public/orgs/db9cb8ff-b606-46cf-bbcd-02c8f8a9a3e2/spaces/6f417400-93ca-41a8-a914-df2ae3981dc6/pages/86dcab0a-ee69-45e8-a045-f4a99f176361/social-card.svg?v=3e7ae33eec8b" alt="Git worktrees" width="600" height="315"></a>A git worktree is a second working copy of your repo on its own branch, sharing the same .git. ForgeDeck gives each running task its own worktree so multiple agents can edit the same repository in parallel without stepping on each other.
How it works
Drag a task to Running → ForgeDeck creates a worktree on a task branch.
The agent's terminal opens inside that worktree, so all its edits are scoped there.
You review the diff for that worktree and merge it back when it's ready.
Finishing the task cleans the worktree up.
Why it matters
No collisions — two agents working at once never clobber each other's files.
Clean review — each task's changes are a self-contained branch + diff.
Safe experiments — abandon a worktree and your main branch is untouched.
Worktrees are the backbone of ForgeSwarm, which fans one goal out across several agents on disjoint file scopes.