factory-worktree

You can achieve conflict-free parallel development by assigning each agent its own isolated git worktree. This provides separate working directories sharing the repository, allowing concurrent edits and independent testing without overwriting files.

Create separate worktrees for each task, run agents in their own directories, and then merge results back. The system handles installing dependencies per workspace, dispatching parallel agents, and cleaning up worktrees after the safe merge.

Yes, this parallel worktree coordination works with both git worktree and jj. It supports environments where multiple agents develop concurrently, test, and merge changes in a shared repository using either version control backend.

Yes, each worktree maintains its own copy of files and state, allowing you to run independent toolchains, servers, tests, and linters per workspace. This isolation ensures concurrent toolchain execution does not cause state conflicts.

Isolated git worktrees are best for parallel feature work, refactoring without overlaps, and running experimental branches. These scenarios benefit from independent toolchains, safe merges, and clean cleanup after concurrent development finishes.