What problem it solves

Git worktrees give parallel AI agents separate working directories, but Git's native worktree workflow requires repetitive commands and branch-name entry. Worktrunk simplifies creating, switching, inspecting, merging, and removing worktrees while adding automation for multi-worktree development.

Key features

• Branch-oriented worktree management — Worktrees are addressed by branch name, with paths computed from a configurable template. Commands that accept a branch also accept the path of its worktree.

  Source: README

• Core commands for parallel changes — Create and switch worktrees, list their status, merge changes, and clean up through a concise command set.

  Source: README

• Workflow automation — Hooks can automate local setup and other worktree events, while merge workflows can squash, rebase, merge, and clean up in one command.

  Source: README

• Worktree status and selection — The list and full-list modes show branch status, commits, CI information, and generated summaries. An interactive picker supports browsing worktrees with status, diff, log, pull request, and comment previews.

  Source: README

• Agent and build-cache support — Commands can launch an agent after switching to a worktree, and copy-on-write build caches can share common build directories across worktrees.

  Source: README

Quick start

Copied verbatim from the project's README.

brew install worktrunk && wt config shell install

$ wt switch --create feature-auth
✓ Created branch feature-auth from main and worktree @ ~/repo.feature-auth

$ 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

Who it may suit

This project may suit developers running several parallel AI coding agents, as well as teams that want to manage many Git worktrees through command-line workflows.

Topics to discuss

• Which local-workflow automations would be most useful through hooks?

• How should parallel-agent worktree status be presented in the terminal?

• Which merge and cleanup workflows should receive more configuration options?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/max-sixty/worktrunk#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.