cd /news/ai-agents/worktrunk-a-cli-for-git-worktree-man… · home › topics › ai-agents › article
[ARTICLE · art-143388] src=worktrunk.dev ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Worktrunk: A CLI for Git worktree management, designed for AI agent workflows

Worktrunk, a new command-line tool for Git worktree management, launched with three core commands — `wt switch`, `wt remove`, and `wt list` — designed to let developers run 5-10+ parallel AI coding agents such as Claude Code and Codex without their changes conflicting. The tool addresses Git's native worktree UX, which requires typing a branch name three times to create and enter a worktree, by addressing worktrees by branch name and computing paths from a configurable template. Worktrunk adds hooks, LLM-generated commit messages, copy-on-write build cache sharing on APFS, btrfs and XFS, and per-worktree dev server ports, and is installable via Homebrew, Cargo, Winget, Arch Linux, and Conda/Pixi.

read4 min views2 publishedOct 1, 2026
Worktrunk: A CLI for Git worktree management, designed for AI agent workflows
Image: source

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows.

Worktrunk’s three core commands make worktrees as easy as branches. Plus, Worktrunk has a bunch of quality-of-life features to simplify working with many parallel changes, including hooks to automate local workflows & copy-on-write build caches.

A quick demo:

Context: git worktrees #

Section titled “Context: git worktrees”

AI agents like Claude Code and Codex can handle longer tasks without supervision, such that it’s possible to manage 5-10+ in parallel. Git’s native worktree feature gives each agent its own working directory, so they don’t step on each other’s changes.

But the git worktree UX is clunky. Even a task as small as starting a new worktree requires typing the branch name three times: git worktree add -b feat ../repo.feat, then cd ../repo.feat.

Worktrunk makes git worktrees as easy as branches #

Section titled “Worktrunk makes git worktrees as easy as branches”

Worktrees are addressed by branch name; paths are computed from a configurable template. Commands that take a branch also accept the path of the worktree it is checked out in.

Start with the core commands

Core commands:

Task Worktrunk Plain git
Switch worktrees wt switch feat cd ../repo.feat
Create + start Claude wt switch -c -x claude feat
git worktree add -b feat ../repo.feat && \
cd ../repo.feat && \
claude

| | Clean up | wt remove |

cd ../repo && \
git worktree remove ../repo.feat && \
git branch -d feat

| | List with status | wt list | git worktree list (paths only) |

Expand into the more advanced commands as needed

Workflow automation:

Multiple parallel agents, same simple commands:

Install #

Section titled “Install”

Homebrew (macOS & Linux):

Shell integration allows commands to change directories.

Cargo:

Windows & other #

Windows. wt defaults to Windows Terminal’s command, so Winget additionally installs Worktrunk as git-wt to avoid the conflict:

Alternatively, disable Windows Terminal’s alias (Settings → Apps → Advanced app settings → App execution aliases → “Terminal”/“Terminal Preview”) to use wt directly.

Free code signing provided by SignPath.io, certificate by SignPath Foundation — policy.

Arch Linux:

Conda / Pixi (community-maintained feedstock):

Or with Pixi: pixi global install worktrunk && wt config shell install.

Quick start #

Section titled “Quick start”

Create a worktree for a new feature:

This creates a new branch and worktree, then switches to it. Do your work, then check all worktrees with wt list:

The @ marks the current worktree. + means staged changes, ↑1 means 1 commit ahead of main, ⇡ means unpushed commits.

When done, either:

PR workflow — commit, push, open a PR, merge via GitHub/GitLab, then clean up:

Local merge — squash, rebase onto main, fast-forward merge, clean up:

For parallel agents, create multiple worktrees and launch an agent in each:

The -x flag runs a command after switching; arguments after -- are passed to it. Configure post-start hooks to automate setup (install deps, start dev servers).

Next steps #

Section titled “Next steps”

── more in #ai-agents 4 stories · sorted by recency
── more on @worktrunk 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/worktrunk-a-cli-for-…] indexed:0 read:4min 2026-10-01 · —