Guide for working in parallel with other agents. Use when another agent is already working in the same directory, or when you need to work on multiple features simultaneously. Covers git worktrees as the recommended approach.
Use git worktrees to work in parallel when another agent is in the same directory.
Git worktrees let you check out multiple branches into separate directories. Each worktree has its own isolated files while sharing the same Git history and remote connections. Changes in one worktree won't affect others, so parallel agents can't interfere with each other.
Learn more: Git worktree documentation
Before running ANY commands in a new worktree, check the project's setup instructions:
claude.md or AGENT.md - Agent-specific guidance if presentproject memory block - Contains learned project preferencesDon't assume npm vs bun vs pnpm -
# Create worktree with new branch (from main repo)
git worktree add -b fix/my-feature ../repo-my-feature main
# Work in the worktree
cd ../repo-my-feature
# CHECK PROJECT SETUP FIRST - then install dependencies
# Read README.md or check project memory block for correct command
bun install # Example - verify this is correct for YOUR project!
# Make changes, commit, push, PR
git add <files>
git commit -m "fix: description"
git push -u origin fix/my-feature
gh pr create --title "Fix: description" --body "## Summary..."
# Clean up when done (from main repo)
git worktree remove ../repo-my-feature
git worktree add -b <branch> <path> main # Create with new branch
git worktree add <path> <existing-branch> # Use existing branch
git worktree list # Show all worktrees
git worktree remove <path> # Remove worktree
../repo-feature-auth, ../repo-bugfix-123Some users prefer cloning the repo multiple times (gh repo clone owner/repo project-01) for simpler mental model. This uses more disk space but provides complete isolation. If the user expresses confusion about worktrees or explicitly prefers clones, use that approach instead.