Price terms as published
Each line is the vendor’s own wording, split from the price capture checked on 2026-09-22. Nothing here is rounded, converted or re-worded — the full sentences stay in the review below. Lines that carry only a price continue the plan named on the line above, in the vendor’s own order.
| # | Plan / term | Checked |
|---|---|---|
| 1 | Free (open source, MIT OR Apache-2.0) | 2026-09-22 |
One-liner: Worktrunk (wt) is a command-line worktree manager built for
developers running several AI coding agents at once, where each agent needs
its own checkout and branches need to be found, synced, and cleaned quickly.
Verified facts (GitHub API + LICENSE + README, 2026-09-22)
| Attribute | Value | Source |
|---|---|---|
| GitHub stars | 8,278 (286 forks, 38 open issues+PRs) | max-sixty/worktrunk via GitHub API, 2026-09-22 |
| License | MIT OR Apache-2.0 (dual, your choice) | LICENSE file text fetched 2026-09-22 + README badge |
| Main language | Rust | GitHub API |
| Created | 2025-10-17 | GitHub API |
| Last push | 2026-09-21 (same-day activity) | GitHub API |
| Docs site | worktrunk.dev | README badge |
The license point needed care and is now settled from primary source: the
GitHub API’s license field reads NOASSERTION (a machine misread the 09-21
review pass flagged), while the repo’s own LICENSE file opens with
“This project is dual-licensed under MIT and Apache-2.0. You may choose
either license at your option.” — we report the file, not the scanner.
The ledger’s earlier ~6.8k star estimate also trails the current API value.
What it does for parallel agents
Plain git worktree commands get unwieldy once half a dozen agents are
working on separate tasks. The README’s core commands are wt switch,
wt list, wt merge, and wt remove — switch creates a branch and
worktree together and jumps into it, list shows all worktrees with CI
status per branch, merge squashes, rebases, merges, and cleans up in one
command, and LLM-generated commit messages come from diffs as a separate
feature. Plus hooks (“run
commands on create, pre-merge, post-merge, etc”), an interactive picker,
and copy-on-write sharing of target//node_modules/ across worktrees on
APFS/btrfs/XFS so ten checkouts don’t mean ten builds. (Note: we have seen
“wt spawn” attributed to this CLI in roundup videos; the current README
names no spawn command — verify command names against the tool itself.)
The catches
- You still need to understand worktrees. The tool reduces friction; it
doesn’t remove the rules of the underlying git model (detached HEADs,
shared
.gitdirectory, uncommitted changes before removal). - Parallel agents share the remote. Multiple agents pushing or touching overlapping files can still collide; worktree isolation is local, not a substitute for task decomposition.
- Young project. Created October 2025 and moving fast — pin versions in automation.
Who should use it
Developers running two or more coding agents in parallel and juggling worktrees by hand; teams scripting agent dispatch who need a stable CLI surface for checkout lifecycle. Single-agent users rarely need it.
Star count, dates, license and feature list verified against the GitHub API, the LICENSE file text, and the current README on 2026-09-22. This entry follows our verification policy: license conclusions come from reading primary source text, not only API metadata. The tool was not executed for this page; no hands-on claims are made.