wtcode

Effortlessly launch your favorite code tool in a git worktree.

worktree code / what-the-code -- streamlines git worktree selection, creation, and launching tools like Claude Code, lazygit, your editor, or any command.

Install

Homebrew

brew install netj/tap/wtcode

PyPI (via uv)

uv tool install wtcode

Or try it without installing:

uvx wtcode

Note: uv tool install is recommended over uvx for regular use. uvx keeps a parent uv tool run process alive, which can interfere with tools like tmux that detect the working directory from the process tree.

From source

git clone https://github.com/netj/wtcode.git
ln -s "$PWD/wtcode/wtcode.sh" /usr/local/bin/wtcode

Usage

wtcode [BRANCH] [CMD [CMD-ARGS...]]
wtcode --exec CMD [CMD-ARGS...]

• BRANCH -- Git branch or worktree name. If omitted and fzf is available, interactively select one. Surround with : to create a new branch (use :::name or name::: to avoid fzf matching the colons).
• CMD -- Command to launch in the worktree. Defaults to $WTCODE_CMD, or the first available of: claude, aider, codex, $SHELL. When CMD resolves to plain claude (no extra args) in a worktree that already existed, wtcode launches claude /resume so it opens straight into your last session there. Press Esc in the picker to start a new session instead.
• --exec -- Skip the branch argument; select interactively via fzf, then launch CMD.
• --help / --version -- Show help or version info.

Examples

wtcode feature-x                  # launch default tool in feature-x worktree
wtcode feature-x lazygit          # launch lazygit
wtcode feature-x claude --resume  # launch claude with flags
wtcode --exec claude --resume     # select interactively, launch claude --resume
wtcode :new-feature               # create new branch and worktree
wtcode                            # interactive branch selection via fzf
WTCODE_CMD=cursor wtcode feature  # use cursor as default tool

Environment variables

How it works

1. Select/specify a branch -- pass as argument or pick interactively with fzf
2. Create or switch to the worktree -- worktrees are organized under $GIT_WORKTREE_ROOT (defaults to ../<repo>.worktrees/)
3. Provision Claude Code, if that's what you're launching -- when the resolved tool is claude, the worktree is auto-trusted (skips the "do you trust this folder" dialog) and .claude/settings.json / .claude/settings.local.json are symlinked in from the main repo if not already present -- never for other tools, never clobbering a file that's already there
4. Launch the tool -- runs the specified command (or smart default) inside the worktree

Dependencies

• git -- required
• fzf -- recommended, for interactive branch selection
• jq -- optional, for Claude Code auto-trust setup (no dependency needed for the settings symlinking itself)

License

MIT