Skip to main content

​
clawker worktree

Manage git worktrees for isolated branch development

​
Synopsis

Manage git worktrees used by clawker for isolated branch development. Worktrees allow running containers against different branches simultaneously without switching branches in your main repository. Each worktree is a separate checkout of the repository at a specific branch. Worktrees are created automatically when using ‘clawker run —worktree <branch>’. Worktree containers mask the main repo’s .git/hooks and .git/config read-only (security measure for unattended sessions): ‘git config —local’ and ‘git remote add’ fail, and ‘git push -u’ still pushes the branch but can’t persist upstream tracking (easy-to-miss warning, exit 0). See https://docs.clawker.dev/worktrees#worktree-caveats

​
Examples

  # Create a worktree for a new branch
  clawker worktree add feat-42

  # Create a worktree from a specific base
  clawker worktree add feat-43 --base main

  # List all worktrees for the current project
  clawker worktree list

  # Remove a worktree by branch name
  clawker worktree remove feat-42

  # Remove a worktree and also delete the branch\n  clawker worktree remove --delete-branch feat-42\n\n  # Preview stale entries that would be pruned
  clawker worktree prune --dry-run

  # Remove stale worktree entries from the registry
  clawker worktree prune

​
Subcommands

​
Options

  -h, --help   help for worktree

​
Options inherited from parent commands

  -D, --debug   Enable debug logging

​
See also

  • clawker - Manage Claude Code in secure Docker containers with clawker