preparing-worktrees

To create an isolated git worktree, the tool automatically selects a project-local directory like .wt/ or worktrees/, creates a new branch, and sets up a reusable workspace. This keeps your main working tree clean and prevents branch contamination during feature development.

Using a project-local directory for git worktrees reduces the risk of contaminating the main working tree. The tool prioritizes .wt/ first, then .worktrees/, then worktrees/, and performs gitignore safety checks to ensure your isolated workspace remains secure and persistent across sessions.

Yes, the tool detects common project files like package.json, Cargo.toml, pyproject.toml, requirements.txt, go.mod, and Gemfile. Upon creating the git worktree, it automatically runs the appropriate project setup commands to prepare the isolated workspace for immediate development.

Managing persistent workspaces across multiple agent runs is handled by wiring up a dedicated git worktree that persists across sessions. This approach supports long-running feature work by integrating with devflow isolation gates, ensuring the base branch remains clean and the workspace state is preserved.

The automation works with existing project configuration files by detecting manifests like package.json, Cargo.toml, pyproject.toml, requirements.txt, go.mod, and Gemfile. It uses these detected files to determine and execute the correct project setup commands automatically within the new worktree.

Manual gitignore configuration is not strictly required because the tool performs automatic gitignore safety checks when selecting project-local locations like .wt/. However, ensuring your gitignore is correctly configured helps maintain a safe and isolated workspace for your feature branches.