wt-core

Portable Git worktree lifecycle manager — a Rust CLI core with thin shell bindings for Nushell, Bash, Zsh, and Fish.

Why

Git worktrees are powerful but clunky. wt-core gives you a fast, consistent interface for creating, navigating, listing, and removing worktrees across every shell you use — without duplicating logic per shell.

All worktree/branch operations live in a single Rust binary. Shell bindings handle only what a subprocess can't: cd in the parent shell.

Commands

wt add <branch> [--base <rev>]   Create a worktree and branch
wt go <branch>                   Switch to an existing worktree
wt list                          List all worktrees
wt remove [<branch>] [--force]   Remove a worktree and its local branch
wt doctor                        Diagnose worktree/repo health

Path Convention

Worktrees are placed under <repo>/.worktrees/ with collision-safe directory names:

<slug>--<8hex>

Example: branch feature/auth → .worktrees/feature-auth--a1b2c3d4/

Output Modes

JSON envelope:

{
  "ok": true,
  "message": "created worktree",
  "repo_root": "/abs/repo",
  "worktree_path": "/abs/repo/.worktrees/feature-auth--a1b2c3d4",
  "cd_path": "/abs/repo/.worktrees/feature-auth--a1b2c3d4"
}

Exit Codes

Shell Integration

Each binding wraps the binary and handles cd in the parent shell.

You can either source files from bindings/ directly, or generate them with wt-core init <shell>.

wt-core init nu > ~/.config/nushell/wt.nu

# ~/.config/nushell/config.nu
source ~/.config/nushell/wt.nu

wt-core init bash > ~/.config/wt/wt.bash
echo 'source ~/.config/wt/wt.bash' >> ~/.bashrc

wt-core init zsh > ~/.config/wt/wt.zsh
echo 'source ~/.config/wt/wt.zsh' >> ~/.zshrc

wt-core init fish > ~/.config/fish/conf.d/wt.fish

Install

cargo install --path .

Then source the appropriate shell binding.

Compatibility

License

MIT