worktrees

Git worktrees create isolated workspaces sharing the same repository, allowing parallel feature development. You can create a worktree under the .worktrees/ directory to sandbox changes without disrupting the mainline workspace or switching contexts.

Managing git worktrees involves creating isolated directories under .worktrees/ and using safety checks for creating, listing, or removing them. This approach keeps feature work separate from mainline while maintaining repo hygiene through quick verification and removal.

Yes, the bd worktree workflow automatically connects to beads via the main BD workflow. After creating a worktree, you can verify beads synchronization by running 'bd ready' within the isolated workspace directory.

To set up a git worktree, first ensure .worktrees/ is in .gitignore, commit the rule, then run 'bd worktree create .worktrees/feature-name'. When done, remove it using 'bd worktree remove .worktrees/feature-name' to maintain repository hygiene.

Ignoring the .worktrees/ directory in .gitignore prevents git from tracking the isolated worktree files in your main repository. This keeps the mainline workspace clean and avoids conflicts when sandboxing feature work across parallel branches.

You should not use git worktrees if your development workflow does not require parallel experimentation or safe separation of changes across branches. Worktrees are designed for deterministic setup scenarios where isolated feature work is necessary without disrupting the main workspace.