站内导读
定位:Worktrunk 是 max-sixty 用 Rust 写的 git worktree 管理 CLI,面向同时运行多个 AI Agent、需要并行隔离工作目录的开发者。
核心能力
- 以分支名寻址 worktree,路径由可配置模板生成,switch、remove、list 三条命令覆盖日常操作。
- switch 支持 -c 建分支、-x 直接启动 claude 等命令,把建目录、切目录、起 Agent 合成一步。
- list 在 git worktree list 的路径之外附带状态信息,便于同时查看多个并行改动。
- 提供 hooks 在创建等阶段执行命令,并支持 copy-on-write 构建缓存,减少重复构建开销。
适用人群:适合已在用 Claude Code、Codex 等 Agent 并行处理任务、熟悉 git 分支与 worktree 概念的开发者,需本地安装 Rust 工具链或预编译二进制。
位置づけ:Worktrunk は max-sixty が Rust で開発した git worktree 管理用 CLI で、複数の AI Agent を並行して動かし、作業ディレクトリを分離したい場面で使います。
主な機能
- worktree をブランチ名で扱い、パスは設定可能なテンプレートから生成。switch・remove・list の 3 コマンドが中心です。
- switch は -c でブランチ作成、-x で claude などの起動まで指定でき、ディレクトリ作成と移動と Agent 起動を 1 回で済ませます。
- list は git worktree list が返すパスに加えて状態も表示し、並行作業の把握に向きます。
- hooks により作成時などにコマンドを実行でき、copy-on-write のビルドキャッシュで再ビルドの負担を抑えられます。
対象となる人:Claude Code や Codex などの Agent を並行利用し、git のブランチと worktree を理解している開発者。Rust ツールチェーンかビルド済みバイナリが必要です。
정체:Worktrunk는 max-sixty가 Rust로 만든 git worktree 관리 CLI로, 여러 AI Agent를 병렬로 실행하며 작업 디렉터리를 분리해야 하는 상황에 씁니다.
핵심 기능
- worktree를 브랜치 이름으로 다루고 경로는 설정 가능한 템플릿으로 계산하며, switch·remove·list 세 명령이 중심입니다.
- switch는 -c로 브랜치를 만들고 -x로 claude 같은 명령을 바로 실행해 디렉터리 생성과 이동, Agent 실행을 한 번에 처리합니다.
- list는 git worktree list가 보여주는 경로에 더해 상태 정보를 함께 출력해 병렬 변경을 파악하기 쉽습니다.
- hooks로 생성 시점 등에 명령을 실행할 수 있고, copy-on-write 빌드 캐시로 반복 빌드 부담을 줄입니다.
대상 사용자:Claude Code, Codex 같은 Agent를 병렬로 돌리며 git 브랜치와 worktree 개념에 익숙한 개발자. Rust 툴체인이나 미리 빌드된 바이너리가 필요합니다.
What it is: Worktrunk is a Rust CLI by max-sixty for managing git worktrees, built for running several AI agents in parallel with separate working directories.
Key capabilities
- Worktrees are addressed by branch name, with paths computed from a configurable template; switch, remove and list cover the daily loop.
- switch takes -c to create a branch and -x to launch a command such as claude, folding directory creation, cd and agent start into one step.
- list reports status alongside the paths that git worktree list shows, which helps when tracking many parallel changes.
- Hooks run commands at stages such as create, and copy-on-write build caches reduce repeated build cost across worktrees.
Who it is for: Developers already running Claude Code, Codex or similar agents in parallel and comfortable with git branches and worktrees; a Rust toolchain or prebuilt binary is required.
README · 详细文档
来源 · 查看原文
Worktrunk
<!-- Crates.io badge below disabled while shields.io is rate-limited by crates.io (renders "CRATES.IO: INVALID"). Tracking: badges/shields#11879. Restore once fixed. 0 --> 1 2 3 4 5 6
November 2026: Worktrunk was released at the start of the year, and has quickly become the most popular git worktree manager. It's built with love (there's no slop!). Please let me know any frictions at all; I'm intensely focused on continuing to make Worktrunk excellent, and the biggest help is folks posting problems they perceive.
Worktrunk is a CLI for git worktree management, designed for running AI agents in parallel.
Worktrunk's three core commands make worktrees as easy as branches. Plus, Worktrunk has a bunch of quality-of-life features to simplify working with many parallel changes, including hooks to automate local workflows & copy-on-write build caches.
A quick demo:

### 📚 Full documentation at worktrunk.dev 📚
Context: git worktrees
AI agents like Claude Code and Codex can handle longer tasks without supervision, such that it's possible to manage 5-10+ in parallel. Git's native worktree feature gives each agent its own working directory, so they don't step on each other's changes.
But the git worktree UX is clunky. Even a task as small as starting a new worktree requires typing the branch name three times: git worktree add -b feat ../repo.feat, then cd ../repo.feat.
Worktrunk makes git worktrees as easy as branches
Worktrees are addressed by branch name; paths are computed from a configurable template. Commands that take a branch also accept the path of the worktree it is checked out in.
Start with the core commands
Core commands:
| Task | Worktrunk | Plain git |
|---|---|---|
| Switch worktrees | wt switch feat |
cd ../repo.feat |
| Create + start Claude | wt switch -c -x claude feat |
|
| Clean up | wt remove |
|
| List with status | wt list |
git worktree list (paths only) |
Expand into the more advanced commands as needed
Workflow automation:
- Hooks — run commands on create, pre-merge, post-merge, etc
- LLM commit messages — generate commit messages from diffs
- Merge workflow — squash, rebase, merge, clean up in one command
- Interactive picker — browse worktrees with streaming CI status and diff, log, PR and comment previews
- Share build caches — ten worktrees get
target/,node_modules/, etc without building or copying them (on APFS, btrfs, and XFS) - 0 — CI status and AI-generated summaries per branch
- PR checkout —
wt switch pr:123to jump straight to a PR's branch - Dev server per worktree —
hash_porttemplate filter gives each worktree a unique port - Aliases & per-branch variables — custom
wt <name>commands and branch-scoped state for hook templates - ...and lots more
Multiple parallel agents, same simple commands:

Install
Homebrew (macOS & Linux):
brew install worktrunk && wt config shell install
Shell integration allows commands to change directories.
Cargo:
cargo install worktrunk && wt config shell install
Windows & other
Windows. wt defaults to Windows Terminal's command, so Winget additionally installs Worktrunk as git-wt to avoid the conflict:
winget install max-sixty.worktrunk
git-wt config shell install
Alternatively, disable Windows Terminal's alias (Settings → Apps → Advanced app settings → App execution aliases → "Terminal"/"Terminal Preview") to use wt directly.
Free code signing provided by SignPath.io, certificate by SignPath Foundation — policy.
Arch Linux:
sudo pacman -S worktrunk && wt config shell install
Conda / Pixi (community-maintained feedstock):
conda install -c conda-forge worktrunk && wt config shell install
Or with Pixi: pixi global install worktrunk && wt config shell install.
Quick start
Create a worktree for a new feature:
$ wt switch --create feature-auth
✓ Created branch feature-auth from main and worktree @ ~/repo.feature-auth
This creates a new branch and worktree, then switches to it. Do your work, then check all worktrees with 0:
$ wt list
Branch Status HEAD± main↕ main…± Remote⇅ Commit Age Message
@ feature-auth + ↑ +27 -8 ↑1 +31 4bc72dc 2h Add authenticatio…
^ main ^⇡ ⇡1 0e631ad 1d Initial commit
○ Showing 2 worktrees, 1 with changes, 1 ahead, hidden: Path
The @ marks the current worktree. + means staged changes, ↑1 means 1 commit ahead of main, ⇡ means unpushed commits.
When done, either:
PR workflow — commit, push, open a PR, merge via GitHub/GitLab, then clean up:
wt step commit # commit staged changes
gh pr create # or glab mr create
wt remove # after PR is merged
Local merge — squash, rebase onto main, fast-forward merge, clean up:
$ wt merge main
◎ Generating commit message and committing changes... (2 files, +53, no squashing needed)
Add authentication module
✓ Committed changes @ a1b2c3d
◎ Merging 1 commit to main @ a1b2c3d (no rebase needed)
* a1b2c3d Add authentication module
auth.rs | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
lib.rs | 2 ++
2 files changed, 53 insertions(+)
✓ Merged to main (1 commit, 2 files, +53)
◎ Removing feature-auth worktree & branch in background (same commit as main, _)
○ Switched to worktree for main @ ~/repo
For parallel agents, create multiple worktrees and launch an agent in each:
wt switch -x claude -c feature-a -- 'Add user authentication'
wt switch -x claude -c feature-b -- 'Fix the pagination bug'
wt switch -x claude -c feature-c -- 'Write tests for the API'
The -x flag runs a command after switching; arguments after -- are passed to it. Configure post-start hooks to automate setup (install deps, start dev servers).
Next steps
- Learn the core commands: 0, 1, 2, 3
- Set up hooks for automated setup
- Explore LLM commit messages, [interactive
picker](https://worktrunk.dev/switch/#interactive-picker), Claude Code integration, CI status & PR links
- Browse tips & patterns for recipes: aliases, dev servers, databases, agent handoffs, and more
- Extending Worktrunk — customize workflows with hooks & aliases
- Watch @DevOpsToolbox's video on Worktrunk
- Run
wt --helporwt <command> --helpfor quick CLI reference
Contributing
- ⭐ Star the repo
- Tell a friend about Worktrunk
- Open an issue — feedback, feature requests, even a small friction or imperfect user message, or a worktree pain not yet solved
- Share: X · Reddit · LinkedIn
### 📚 Full documentation at worktrunk.dev 📚
Star history
<!-- sealed_token is a GitHub token of ours encrypted with star-history's public key, from "Generate embed code" on star-history.com. Without one the chart renders a "GitHub restricted access to star data" placeholder: GitHub limits stargazer data to a repo's admins and collaborators, and their servers are neither.
The token is fine-grained and reaches only this repo. Its Contents permission has to be read and write — write access is what GitHub accepts as proof of collaborator status, so rotating to a read-only token brings the placeholder straight back. Publishing the ciphertext is safe on its own; what the scope buys is a bound on star-history, which decrypts it and so holds a credential that can push here until it expires 2027-08-16 — at which point the chart reverts to the placeholder with nothing else to signal it. star-history reports GitHub is working on restoring access, so drop this parameter once the plain URL renders a chart again. -->