using-git-worktrees

To isolate feature development, you can create a clean directory using native workspace tooling, or fall back to a git worktree if native tools are unavailable. This ensures your feature work happens in an isolated workspace.

A git worktree is a native mechanism that creates an isolated directory for your feature work. You should use it as a fallback when your platform's native workspace isolation tools are not available.

You need to run an isolation detection process before creating a new workspace. The workflow automatically skips creating a new isolated directory if it detects that your environment is already properly isolated.

No, you do not need native workspace tooling. The setup prefers native tools when available, but automatically falls back to creating a manual git worktree with project-local ignore checks and basic setup validation.

The best way to manage consent and guardrails is to use a workflow that respects existing user preferences before creating isolation. It validates the clean baseline setup and reports the workspace status to ensure safe feature development.

Git worktree setup validation fails when the baseline is not clean or project-local ignore checks are not properly configured. The workflow requires basic setup validation to report a successful isolated workspace status.