worktree-per-pr

Git state isolation for concurrent agentic tasks is achieved by managing isolated, ephemeral worktree lifecycles for every sub-agent dispatch. This ensures strictly separated project checkouts, eliminating the risk of edits bleeding across concurrent jobs.

Running multiple agents reviewing different pull requests without conflicts requires creating distinct, per-dispatch worktree checkouts. This provides each agent with a clean environment, preventing file corruption and git-push conflicts during concurrent operations.

Setting up a fresh isolated worktree for an agent dispatch involves using the worktree-per-pr skill within the garden's dispatch architecture. It handles the setup and teardown of worktree triples to prepare clean, ephemeral environments.

Git worktree lifecycle management does automatically clean up stale artifacts after a task completes. It orchestrates the strict setup and teardown of ephemeral workspaces to ensure no residual files remain and workspace integrity is maintained.

Ephemeral worktrees are needed when executing mutating and read-only subagents concurrently within a dispatch architecture. They provide the strict isolation required to prevent cross-job interference and state corruption during parallel task execution.