Git Worktrees for Parallel AI Agent and Human Branches

This post was created with AI assistance and reviewed for accuracy before publishing. Trending in 2026: “agent runs” are normal. You might kick off a long AI coding agent job on a feature branch while you fix a production bug elsewhere. Git worktrees let you keep two checkouts of the same repository without a second clone, sharing objects on disk. Why agents make worktrees matter Agent runs often leave dirty trees, build artifacts, or lockfiles mid-flight. Stashing works but is easy to forget. A second worktree at./my-repo-hotfix checked out to main keeps your mental model clean.