git-wt — Git Worktree Manager

git-wt

~/.git-wt/<repo>/<name>/

.gitignore

Prerequisites

git-wt

git wt --version

Commands Reference

Create a worktree

git wt new                           # Auto-named (e.g., swift-jade)
git wt new my-feature                # Named
git wt new -b main hotfix            # Fork from specific branch
git wt new --copy-env experiment     # Copy .env* files into worktree
git wt new --no-branch scratch       # Detached HEAD (no branch created)

Navigate to a worktree

cd $(git wt path <name>)             # Jump into worktree
git wt open <name>                   # Open in Cursor/VS Code/$EDITOR

List worktrees

git wt list                          # Worktrees for current repo
git wt list-all                      # Worktrees across ALL repos

Find the main repo

git wt origin                        # Print main repo path (from any worktree)

Remove worktrees

git wt rm <name>                     # Remove worktree + delete its branch
git wt clean                         # Remove ALL worktrees for current repo

Key Details

• Storage:

  ~/.git-wt/<repo>/<name>/

  — outside the repo, globally managed
• Branches: prefixed

  wt/

  by default (e.g.,

  wt/my-feature

  )
• Naming: auto-generates

  adjective-noun

  names if no name given

• rm

  : removes both the worktree directory and its git branch

• --copy-env

  : copies all

  .env*

  files from repo root (critical for dev servers)

• origin

  : prints main repo path — works from any worktree or main repo itself

Environment Variables

• GIT_WT_HOME

  — Root directory for all worktrees (default:

  ~/.git-wt

  )

• GIT_WT_PREFIX

  — Branch name prefix (default:

  wt

  )

When to Use

git wt new

• Working on a separate task that needs isolation from current work
• Running parallel agents that each need their own repo copy
• Experimenting without affecting the current branch
• Needing to quickly switch context between features

git wt new --copy-env

• The project has

  .env

  files needed for the dev server to start
• The worktree needs the same configuration as the main repo

Workflow: Parallel Agent Isolation

# Agent 1: create isolated worktree
git wt new --copy-env task-auth

# Agent 2: create another
git wt new --copy-env task-api

# Each agent works independently in their worktree
cd $(git wt path task-auth)

# When done
git wt rm task-auth
git wt rm task-api