Tools/max-sixty/worktrunk

worktrunk

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

10.2k ★+661/wkgrowthRustMIT OR Apache-2.0trending

The Lens

By Erik Loyd, SaaS CEO and former COO/CFO of an AWS Premier Partner.

Updated Oct 2026

Worktrunk makes Git worktrees as easy as branches. A worktree is an extra checkout of your repo in its own folder, so several AI coding agents can work at once without trampling each other. Plain git worktree makes you type the branch name three times; wt switch -c -x claude feat creates both and launches Claude Code in one line. It's a free Rust CLI, dual-licensed MIT or Apache 2.0.

Nothing to host. Install it (Homebrew, Cargo, winget and others), then run wt config shell install so it can change directories. On Windows, wt collides with Windows Terminal, so winget also installs it as git-wt. It has outgrown a wrapper: lifecycle hooks, one-command squash and merge, LLM commit messages through whatever CLI you already use, CI status in wt list --full, and copy-on-write sharing of node_modules or target/ on APFS, btrfs and XFS. No paid tier: solo, small teams and larger teams all run it free.

The catch: it's pre-1.0 and churns. The October release listed 13 breaking changes across hooks, templates and config paths, so pin a version. It's essentially one maintainer. Project hooks in a repo's .config/wt.toml run shell commands; worktrunk asks first, but --yes skips the prompt.

Free vs Self-Hosted vs Paid

fully free

Free: Everything. Dual-licensed MIT OR Apache-2.0, distributed through Homebrew, Cargo, winget, pacman and conda-forge.

Self-hosted: Nothing to host. It's a local CLI binary that drives your existing git install. Optional LLM commit messages pipe a prompt to a command you configure (Claude Code, Codex, llm, aichat, opencode), so any cost is whatever that model already charges you.

Paid: No paid tier, no hosted version, no account.

Completely free. The only possible cost is the LLM behind optional commit-message generation, billed by whichever CLI you point it at.

What to do by team size

Solo
free; install the binary and the shell integration
Small team
free; commit a shared .config/wt.toml for project hooks
Medium team
free; pin a version, since minor releases carry breaking changes
Large team
free; review project hooks before anyone runs with --yes in automation
Self-hosting ops:trivial

Get tools like this every Wednesday

One featured tool, three on the radar. No fluff.

Score
82/100 · A
Adoption25/30
Maintenance25/25
Community7/20
License15/15
Analysis10/10

A low score is not a verdict on quality. Young and niche tools start low by design. How we calculate scores

Trust Signals

Notable author: 1,198 followers

About

Owner
Maximilian Roos (User)
Stars
10,188
Forks
368

Explore Further

More tools in the directory