Rank #06 · Daily · DevTools
worktrunk: Git Worktree CLI Built for Parallel AI Agents
Treat worktrees like branches: wt switch -c -x claude feat instead of typing the branch name three times with raw git worktree.
What it does
Worktrunk addresses worktrees by branch name (paths come from a configurable template). Core loop from the README:
wt switch/wt switch -c— jump to or create a worktree;-xruns a command after switch (for example launch Claude Code).wt list— status-rich listing (staged changes, ahead/behind, remote sync), not just paths.wt remove/wt merge— tear down or squash-rebase-merge in one flow.- Hooks on create, pre-merge, post-merge, and related events for install deps / start servers.
- Copy-on-write build caches (
target/,node_modules/, etc.) on APFS, btrfs, and XFS so many worktrees don't rebuild from scratch. - Extras: LLM commit messages, interactive picker with CI/PR previews,
wt switch pr:123, per-worktree ports viahash_port, aliases.
Install via Homebrew, cargo, winget (git-wt on Windows to avoid clashing with Windows Terminal's wt), Arch, or conda-forge. Docs: worktrunk.dev.
Who it's for
Developers running several coding agents in parallel (Claude Code, Codex, and similar) who outgrew one dirty working tree; anyone already using git worktrees who wants less path bookkeeping.
Stars / language / license
10,501 stars · Rust · MIT OR Apache-2.0
Data verified: 2026-11-04 09:13 Asia/Shanghai (GitHub API get_repository + LICENSE get_file_contents; GitHub API license field reports Other / NOASSERTION for dual-license repos)
Trending note: +438 stars today (Trending selection captured 09:12 Asia/Shanghai)
Category tags
DevTools · git · worktrees · agents · Rust · CLI · Claude-Code
How it differs from similar projects
Plain git worktree. Same underlying feature; Worktrunk collapses the multi-step create/cd/remove path and adds status, hooks, merge workflow, and agent launch flags.
Generic branch switchers / IDE multi-root. Those usually stay inside one checkout. Worktrunk's unit of isolation is a full worktree directory — which is what parallel agents need when they edit files concurrently.
Agent orchestrators that spawn containers. Heavier isolation; Worktrunk stays in git's native model on the host filesystem.
No independent benchmark of agent throughput is claimed here — the value is UX and workflow automation around git's existing worktree mechanism.