forking-worktree

To create isolated git worktrees, you fork a new autonomy branch from a suitable point and place it under .worktrees/autonomy/ at the repository root, ensuring the main working directory remains intact for parallel agent workloads.

Using git worktrees is the best way to run parallel agent workloads without disturbing the main git branch, as it creates separate directories for different strategies while keeping the main working directory safe and isolated.

You set up a new autonomy branch from a specific fork point by creating a dedicated worktree, which automatically generates a branch named autonomy/<strategy-name> and isolates the changes in a separate directory.

Creating parallel worktrees does not impact your current working directory, because the process safely isolates new autonomy branches under the .worktrees/autonomy/ path while leaving the main branch completely intact.

Parallel worktrees are stored under the .worktrees/autonomy/ directory at the repository root, ensuring consistent placement and easy access when switching between different parallel agent workloads.

You need to use git worktrees for branch management when you want to run multiple agents simultaneously, allowing each agent to iterate on a different strategy in its own isolated directory without causing conflicts.