Q
When should agents share one workspace?
Only when the partition is genuinely disjoint, separate files with no shared symbols. When in doubt, worktree; the merge gate is cheaper than a corrupted tree.
Glossary · Worktree Placement
Worktree Placement.
Git-native isolation without the clone tax.
Direct answer
Worktree placement gives each agent its own git worktree, a second checkout sharing the repository's object database, so concurrent edits never collide in one working tree while disk and fetch cost stay low. It sits between shared placement (one workspace, cheapest, fine for clean partitions) and clone placement (fully separate checkout, strongest isolation, highest cost). Swarm runs choose placement per job; merge conflicts are surfaced at the integration gate, not discovered mid-edit.
In Anvaya
How We Implement It.
01Worktree PlacementAnvaya's defect, mvp and refine bundles default to worktree placement; the integration gate lands approved work on anv/integration/<run>. The production E2E delivered three SaaS apps this way with zero conflicts.
Questions
Asked About Worktree Placement.
Q
What does the integration gate check?
Verdicts per task plus the integration build and tests on the run branch. Conflicts and failed verdicts are parked and reported, not silently dropped.
Q
Does worktree placement need special tooling?
No, it is plain git. The supervisor manages creation, publishing refs and garbage collection; recovery commands exist for crashed workspaces.
Run Agents That Fit On Your Laptop.
25.6 MB median RSS. 25 agents ran in parallel on a Core 2 Duo with 4 GB RAM. Hundreds on your machine. Zero cloud required on the Ollama path.
Requires Rust/cargo to build from source. Linux and macOS today, Windows not yet supported. Pre-1.0, public beta. Pricing TBD.