Worktrunk folds git worktree into three core commands: run 5–10 AI agents in parallel, each in its own directory
Synopsis
Worktrunk is a command-line tool for managing git worktrees, built for running AI agents in parallel, and since its release early this year it has become the most popular git worktree manager. It targets the clunky native git worktree experience, where even starting a new worktree means typing the branch name three times and then changing directory by hand. Worktrunk uses three core commands to bring worktree handling close to ordinary branch operations, addresses worktrees by branch name with paths computed from a configurable template, and adds hooks, a merge workflow and shared build caches.
Interpretation
Worktrunk folds git worktree management into three core commands, so creating, switching to and listing worktrees sits close to everyday branch operations. The native git worktree experience is clunky: even starting a new worktree requires typing the branch name three times and then entering the new directory manually. In the demo, a single wt switch --create feature-auth command creates a branch and worktree from main and switches to it, after which wt list shows each worktree's branch, commits ahead and change status.
Worktrees are addressed by branch name, paths are computed from a configurable template, and commands that take a branch also accept the path of the worktree it is checked out in. Native git requires remembering both the branch name and the directory path, and both appear separately in commands. wt list output marks the current worktree with @ and shows each branch's commits and change status.
For parallel changes, the tool offers hooks, commit messages generated from diffs, a merge workflow that squashes, rebases, merges and cleans up in one command, an interactive picker with CI status and diff previews, and shared build caches on APFS, btrfs and XFS. These features target operations that recur when handling several worktrees in parallel, such as build caches, commit messages and merge cleanup. Shared build caches let ten worktrees use target/, node_modules/ and similar directories without building or copying them, a capability limited to the APFS, btrfs and XFS filesystems.
Perspective
The demonstrated scope is creating, switching to, listing and removing git worktrees, plus supporting features such as hooks, a merge workflow, an interactive picker and shared build caches; shared build caches are explicitly limited to the APFS, btrfs and XFS filesystems. The intended reader is a developer using git who needs to manage several working directories in parallel.
The material calls Worktrunk the most popular git worktree manager but gives no measure or comparison data; managing 5–10 or more agents in parallel is described as possible rather than as a measured capacity result.
