Key takeaways
- Run several AI coding agents side by side, each in its own git worktree, addressed by branch name rather than by path.
- Automate setup and tidy-up: hooks run commands when worktrees are created or merged, and a merge workflow cleans up after you.
- Pick between worktrees with an interactive picker that shows streaming CI status, and share build caches on supported filesystems.
- The catches: the GitHub API does not state a licence, the command name clashes with Windows Terminal, and cache sharing needs certain filesystems.
- We did not run it. Everything here comes from the project's README and the GitHub API.
What it is
Worktrunk is a command-line tool for git worktree management, designed for running AI agents in parallel, according to its README. The project is written in Rust and is public on GitHub at max-sixty/worktrunk.
The problem it solves
The README says agents such as Claude Code and Codex can handle longer tasks without supervision. Git's worktree feature gives each agent its own working directory, so they do not step on each other's changes.
The trouble, in the project's own words, is that the everyday git worktree experience is clunky. Developers who run several agents at once are the people most likely to feel that friction.
What you get
- Simpler addressing: worktrees are addressed by branch name, with paths computed from a configurable template.
- Automation: hooks run commands on events such as creating or merging a worktree.
- Less cleanup: a merge workflow squashes, rebases, merges and cleans up in one command.
- Easier navigation: an interactive picker browses worktrees with streaming CI status and previews of diffs, logs and pull requests.
- Faster starts: build caches can be shared between worktrees without building or copying them, on APFS, btrfs and XFS filesystems.
The catches
- Licence: the GitHub API does not state a clear licence and lists it as Other. A badge in the README reads MIT OR Apache-2.0, but the API does not confirm it, so check the repository before relying on it.
- Windows: the short command name defaults to Windows Terminal's command, so Windows users need a different route to avoid the clash.
- Setup: shell integration is needed so that commands can change directories.
- Filesystems: shared build caches are described only for APFS, btrfs and XFS.
- Claims: the README says it has quickly become the most popular git worktree manager. That is the project's own claim and we did not verify it.
What we did not test
We did not run Worktrunk, install it, launch an agent with it or check its merge and cache features. Every claim here comes from a literal quote in the project's README or the GitHub API, and the feature descriptions are the project's own.
Verdict
Editors' view: this is for developers who already run several coding agents against one repository and find plain git worktrees tedious. If you use one agent at a time, it is probably more tooling than you need. Settle the licence question first if you plan to use it commercially.
Sources
Need help adopting this, or have a software project in mind?
Tell us what you are building. The initial consultation is free. Email [email protected] or follow @zolnaltd.
Start a conversation →