Worktrunk Wraps Git Worktrees for 5 to 10 Parallel Coding Agents, While Git's Manual Still Calls Multiple Checkout Experimental

Worktrunk, a command-line tool that manages Git worktrees so several AI coding agents can work in one repository at once, gained 77 stars in a day and shows about 10,100 in total. Git's own manual for the feature it wraps says that "Multiple checkout in general is still experimental, and the support for submodules is incomplete."

The tool is published by the GitHub user max-sixty under MIT OR Apache-2.0, and the repository shows 5,475 commits, 43 open issues and 25 open pull requests. The README says it has "quickly become the most popular git worktree manager," which is the author's description and not a measurement this report could check. Stars are not users.

What problem it addresses

The README's pitch is that agents such as Claude Code and Codex can run unsupervised on long tasks, so a developer may have 5 to 10 or more going at once. A Git worktree gives each its own working directory attached to the same repository. Git refuses by default to add a worktree for a branch that another worktree already has checked out, which stops two agents editing the same branch unless someone passes force.

The raw commands are verbose. The README's example is that creating a branch and a worktree means typing the branch name three times. Worktrunk addresses worktrees by branch name and derives paths from a configurable template.

The commands

Command	What it does
wt switch -c	Create a branch and worktree, then change into it
wt switch -x claude	Run a command, here Claude Code, after switching
wt list --full	Show worktrees with CI status and AI-generated summaries
wt merge	Squash, rebase, merge and clean up
wt switch pr:123	Check out a pull request's branch

Hooks run commands on create, pre-merge and post-merge, and the README mentions post-start hooks for installing dependencies or starting dev servers. Installation is brew install worktrunk, cargo install worktrunk, or on Windows winget install max-sixty.worktrunk, which installs the binary as git-wt because wt collides with Windows Terminal.

What Git's manual limits

The manual says an unclean worktree, meaning one with untracked files or modifications, cannot be removed without force, and the same holds for one with submodules. A locked worktree needs force given twice. Git warns that making multiple checkouts of a superproject is not recommended.

Those limits matter more once agents create worktrees faster than a person reviews them. If a worktree is deleted without git worktree remove, Git eventually prunes its administrative files under the gc.worktreePruneExpire setting.

What the issue tracker shows

Issue #4544, opened October 21, asks for a stash on wt remove -f, with 3 comments. The title suggests the concern is forced removal discarding work, though the page shows titles and not bodies. Issue #4585 reports lost results with expensive merge drivers and orphaned merge-tree processes.

Two hook issues stand out. Issue #4654, opened November 2, reports that Codex repeatedly asks the user to review and trust Worktrunk activity hooks. Issue #4142 notes that a hook failure always suggests --no-hooks, including when the failing hook is a pre-merge gate. Issue #3921 reports that plugin marker hooks follow the shell's working directory, so a cd mid-session can mark the wrong repository.

Caveats in the README itself

The feature that shares build caches, so that "ten worktrees get target/, node_modules/, etc without building or copying them," works only on APFS, btrfs and XFS. The LLM-based features, commit messages and summaries, need a model, and the README does not detail the setup. It also calls the code "built with love (there's no slop!)", a self-description. The banner is dated November 2026 yet says the project was released at the start of the year.

A developer running a handful of agents on a Mac or a btrfs Linux box gets the most from it. One on ext4 should expect no cache sharing, and anyone on Windows should use the git-wt name. Readers tracking agent tooling that has moved fast and other repositories that surged on GitHub will recognise the pattern. Issue #4544 is the one to watch before using forced removal.