clawker worktree
Manage git worktrees for isolated branch developmentSynopsis
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
Subcommands
- clawker worktree add - Create a worktree for a branch
- clawker worktree list - List worktrees for the current project
- clawker worktree prune - Remove stale worktree entries from the registry
- clawker worktree remove - Remove one or more worktrees
Options
Options inherited from parent commands
See also
- clawker - Run coding agents in secure Docker containers with clawker