ForgeSwarm
Run many agents on one repo without chaos — decompose, materialize, gated merge.
Embed
<a href="https://docs.forgedeck.net/swarm"><img src="https://docs.forgedeck.net/_api/public/orgs/db9cb8ff-b606-46cf-bbcd-02c8f8a9a3e2/spaces/6f417400-93ca-41a8-a914-df2ae3981dc6/pages/922849b7-0c20-41a6-a984-6646a96375b4/social-card.svg?v=3e7ae33eec8b" alt="ForgeSwarm" width="600" height="315"></a>ForgeSwarm takes a single goal and runs several agents on it at once — without the chaos of agents fighting over the same files.
How it works
Decompose — the goal is split into sub-tasks with disjoint file scopes, so no two agents touch the same files.
Materialize — each agent gets its own git worktree on its own branch.
Launch — agents run in parallel, each in its own pane, coordinated through a mailbox.
Gated merge — completed work is merged back through human-gated review, one worktree at a time.
Why disjoint scopes
Overlapping edits are where multi-agent setups fall apart. By assigning non-overlapping file ownership up front, swarm worktrees never collide on merge — review stays clean and the result is deterministic.
ForgeSwarm builds on the same primitives as the rest of ForgeDeck: agents, worktrees, and the board.