Who it is forA developer managing 5 to 10 agents who is tired of typing branch names three times.
The problemAgents in one directory step on each other's changes, and plain git worktree commands are clunky.
The outcomeOne worktree per agent, each started with a task, addressed by branch name.
What you need first
- git
- Homebrew or Cargo to install
- Shell integration via `wt config shell install` so commands can change directories
- An agent such as Claude Code or Codex
Steps
- Run
brew install worktrunk && wt config shell install(orcargo install worktrunk && wt config shell install) - Run
wt switch -x claude -c feature-a -- 'Add user authentication' - Run
wt switch -x claude -c feature-b -- 'Fix the pagination bug' - Run
wt listto see the status of each worktree
Prompt for your agent
Install worktrunk, then for each of <tasks> run `wt switch -x claude -c <branch> -- '<task>'` so every agent gets its own worktree. Use `wt list` to report status.
Caveat. On Windows, winget installs it as git-wt to avoid a clash with Windows Terminal's wt command.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for max-sixty/worktrunk and "Run several coding agents in parallel worktrees"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer