Worktrunk v0.82.0

Worktrunk is an open-source command-line tool that simplifies Git worktree management, especially for developers running multiple AI coding resources at the same time. Built by Max Sixty, it is a convenient interface for creating, modifying, registering, joining, and deleting active worktrees without having to use lengthy Git commands.

Git work trees allow multiple branches from the same repository to have separate working directories. This is especially useful when agents like Claude Code and OpenAI Codex are run in parallel, as each agent can work independently without affecting the other agent’s files.

Worktrunk builds on this functionality with additional automation, collaborative navigation, and development workflow features.

Features

Simplified Git Worktree Management

Worktrunk provides three core commands for everyday worktree operations:

  • wt switch switches between existing worktrees or creates new ones.

  • wt list displays worktrees with branch status and change information.

  • wt remove removes worktrees and their associated branches.

For example, creating a new feature branch and worktree requires only:

wt switch --create feature-auth

Worktrunk automatically creates the branch, prepares its working directory, and switches the shell into it.

This eliminates much of the repetitive work involved in managing Git worktrees manually.

Parallel AI Coding Agents

Worktrunk is particularly useful for developers working with multiple AI coding agents.

It can create a worktree and immediately launch an agent using the -x option:

wt switch -x claude --create feature-a -- "Implement user authentication"

Developers can repeat this process for different tasks, giving each agent its own branch and working directory.

This approach works with different command-line coding agents, including Claude Code and Codex. Worktrunk does not provide its own AI model or require users to replace their existing coding tools.

Automated Development Hooks

Worktrunk includes configurable hooks that execute commands during different stages of the worktree lifecycle.

Examples include:

  • Pre-start hooks for installing dependencies.

  • Post-start hooks for preparing development environments.

  • Pre-merge hooks for running tests and validation.

  • Post-merge hooks for cleaning up temporary resources.

Hooks can automate repetitive setup tasks whenever a new worktree is created.

For projects using Node.js, developers can configure dependency installation automatically. Other workflows can prepare databases, environment files, development servers, or additional resources.

Interactive Worktree Picker

Worktrunk provides an interactive interface for navigating existing worktrees.

Instead of remembering branch names and directory paths, developers can browse available worktrees and inspect their status.

The picker can display additional information, including Git diffs, commit history, pull requests, comments, and CI status.

This becomes increasingly useful when managing many parallel development tasks.

Shared Build Caches

One challenge with Git worktrees is that each working directory can require its own dependency installation and build output.

Worktrunk addresses this through copy-on-write build cache sharing.

It supports sharing directories such as node_modules/ and Rust's target/ across worktrees on supported filesystems, including APFS, Btrfs, and XFS.

This can significantly reduce redundant disk usage and avoid repeatedly rebuilding dependencies.

The feature depends on filesystem support and appropriate configuration. It should not be assumed to work identically on every operating system or storage configuration.

Git Merge and Cleanup

Worktrunk provides a simplified merge workflow that can handle committing, rebasing, merging, and cleaning up a completed worktree.

For example:

wt merge main

The command can prepare changes, generate a commit message when configured, merge the branch into the target, and remove the completed worktree.

This reduces the number of manual Git operations required to finish a development task.

Pull Request Integration

Worktrunk supports switching directly to pull request branches.

For example:

wt switch pr:123

It can also display CI status and pull request information through its listing and interactive navigation features.

This makes it easier to move between local development branches and remotely hosted contributions.

Custom Commands and Configuration

Worktrunk supports aliases, custom commands, configurable worktree paths, and per-branch variables.

Developers can use these features to build project-specific workflows without maintaining separate shell scripts for every operation.

Its configuration system also supports LLM-generated commit messages, allowing developers to generate commit descriptions from their changes when an appropriate AI tool is configured.

Download Worktrunk v0.82.0 - Software Mirrors

Worktrunk v0.82.0 for Windows

worktrunk-x86_64-pc-windows-msvc.zip | 16.9 MB

Worktrunk v0.82.0 for macOS

worktrunk-x86_64-apple-darwin.tar.xz | 7.01 MB

worktrunk-aarch64-apple-darwin.tar.xz | 6.39 MB

Worktrunk v0.82.0 for Linux

worktrunk-x86_64-unknown-linux-musl.tar.xz | 8.03 MB

worktrunk-aarch64-unknown-linux-musl.tar.xz | 7.16 MB

Others Download related to Worktrunk v0.82.0

wt.rb | 2.58 kB

worktrunk-installer.sh | 52.25 kB

worktrunk-installer.ps1 | 20.86 kB

source.tar.gz | 3.99 MB

sha256.sum | 610 B

Worktrunk v0.82.0 Source Code

Worktrunk v0.82.0 Source code (zip)

Worktrunk v0.82.0 Source code (tar.gz)

Worktrunk v0.82.0 Release Notes:

Release Notes

Improved

  • Backups before forced removal: wt remove --force snapshots the worktree, including untracked files, to refs/wt-backup/ and prints a recovery command. Ignored files, changes inside submodules, and separate staged versions are excluded. A failed backup stops removal; an unreadable status still permits removal without one. Docs (#4545, thanks @yajo for #4544)
  • Codex activity hooks ship separately: skills stay in worktrunk; activity hooks move to worktrunk-markers, so skill updates don't trigger hook reapproval. (Breaking: existing installs need codex plugin add worktrunk-markers@worktrunk to retain activity markers after updating.) Docs (#4707, thanks @win5do for #4654)
  • Claude Code /wt-diff pane: shows the branch diff for worktrees the session has worked in, including work detected from subagents. Failed worktree lookups are retried, and tool errors reach Claude's hook diagnostics. Docs (#4638, #4668, #4689, thanks @rudycelekli and @Yash2031v)
  • Shell completion: typing wt switch origin/ completes that remote's branches. Hook names honor per-project user overrides and source-qualified filters; completion honors -C, --config, config overrides, and alias precedence over executables on PATH. PowerShell filters suggestions by the typed prefix. (#4613, #4549, #4551, #4548, #4560, #4721, thanks @Bortlesboat, and @thernstig for #4612)
  • JSON survives later failures: commands retain confirmed results when a later step fails, while diagnostics go to stderr and the exit status signals failure. wt switch --format=json emits one result after execution. List schema 1 reports the tracked remote branch when its name differs locally. (#4345, #4574, #4584, #4756)
  • Removal feedback: failures describe the surviving checkout and branch. --delete-branch is visible in help as the override for delete-branch = false, and the picker briefly confirms successful Alt-x removal. (#4457, #4615, #4669, thanks @Yash2031v for the picker feedback and @cazador481 for #4614)
  • Fewer repeated Git operations: committing skips the second staging pass when no pre-commit hook ran; concurrent list tasks share identical ahead/behind counts. (#4540, #4663)

Fixed

  • Copying ignored files: .worktreeinclude can select paths inside wholly ignored directories, such as .cache/types/. Copy and promotion also enforce destination containment before creating directories or moving files. (#4751)
  • Foreground cancellation: signal handling closes races around child startup and completion, so Ctrl-C stops subsequent command steps. On Unix, wt step tether stops its supervised processes on interruption and now propagates a command's failure status. (#4596, #4609, #4623, #4598, thanks @drldavis for #4622)
  • Hook execution and feedback: unselected templates no longer cause errors or consume arguments. Filtered background hooks retain independent user and project pipelines, and template failures identify the command. Background hooks running in different directories receive separate announcements. (#4429, #4781)
  • Config loading: rejected environment overrides warn and fall back to file settings consistently across commands; unreadable config files are reported instead of silently ignored. System-config deprecations point to the file that needs editing. (#4358, #4564, #4767)
  • State values: clearing a key removes all repeated values. Branch-local reads and clears exclude variables belonging to branches whose names extend with .vars.*. State tables preserve literal pipes, links, and formatting characters. (#4566, #4779, #4780)
  • Log and terminal handling: authentication-probe output is redacted from diagnostics; Unix logs use private permissions, and permission repair leaves symlink targets unchanged. Commit subjects, PR context, and list summaries escape terminal control characters. (#4604, #4611, #4605, #4730)
  • SSH remotes with a non-default port: port-less legacy project IDs no longer supply approvals or project settings to a different SSH server. Those repositories need port-qualified approvals and project overrides. (#4606)
  • Removal with submodules: text-mode removal warns about submodule commits reachable from no remote; the warning does not prevent removal. Orphan cleanup preserves fsmonitor daemons serving live submodules. (#4460, #4729)
  • Fork branch conflicts and GitHub Enterprise: GitLab and Azure DevOps use a prefixed, fetch-only branch when a fork's branch name conflicts locally. GitHub Enterprise PR lookup uses the remote’s host, or a supplied PR URL’s host, when gh is authenticated there. (#4542, #4710, #4722, thanks @anqorithm, and @pgilad-rna for #4709)
  • Azure DevOps remotes: collection-prefixed URLs, legacy SSH URLs, and URLs omitting the project segment resolve the correct project for links and CI lookup. (#4764, thanks @owpac for #4763)
  • Shell integration: directory changes preserve trailing spaces, and PowerShell treats paths containing brackets literally. Installation continues configuring other shells after an rc-file error; uninstall matches recognized standalone setup lines and leaves customized lines for manual removal. (#4608, #4680, #4583, #4595, thanks @dajiaohuang for the PowerShell fix and @lucasfonte21 for #4582)
  • Agent plugins: Claude's worktree-switching skill leaves the current worktree session before entering another by path. On Windows, Pi, oh-my-pi, and OpenCode select Worktrunk rather than Windows Terminal's wt; Claude activity markers are written without launching another wt. (#4714, #4698, #4619, thanks @tian-yu200 for #4697)
  • Branch markers: deleting a branch through Worktrunk or creating it with wt switch --create clears its marker, so reused names don't inherit stale activity. Clearing all markers preserves a state variable named marker. (#4684, #4704, #4528, thanks @wsgavin for #4683)
  • List and picker display: headers use @ for HEAD and ^ for the default branch. Variation-selector emoji align; IPv6-only loopback servers are detected; the footer shows task progress; stale refreshes cannot overwrite removal layout. (#4682, #4694, #4620, #4708, #4732, thanks @nixpulvis for #4727, @saltcoffee for the IPv6 fix and @NorfeldtKnowit for #4681)
  • Numeric custom columns: list-column validation accepts int and float filters on vars. and git.branch. values. (#4775, thanks @adrian-gierakowski for #1983)
  • Linux process cleanup: wt remove --reap discovers process working directories through /proc, avoiding a timed-out system-wide lsof scan. (#4631, thanks @OmerFarukOruc for #4630)
  • Aliases and custom commands: named aliases can be inspected outside a repository; project aliases display migrated template variables. Custom-command discovery excludes non-executable entries. (#4547, #4690, #4565)
  • Fixes for unusual setups: slash-named remotes work in branch inventory; same-named tags don't affect the push range; non-UTF-8 environment entries no longer panic config loading; invalid alias arguments cannot fall through to a PATH executable; failed Git ref queries propagate as errors. (#4271, #4499, #4563, #4550, #4562, thanks @Duang777)

Documentation

  • Claude desktop worktrees: clarifies that the desktop app skips the plugin’s worktree hooks, so its worktree sessions bypass Worktrunk. Docs (#4777, thanks @chatoo2412 for #4776)
  • Guides and examples: guides explain shortened list counts and the default base branch for Claude’s hook-created worktrees. Skill anchors and site icon links are repaired; the move-changes alias stops if stashing or restoring fails. (#4575, #4576, #4688, #4678, #4770, #4751, #4719, thanks @viwe-monai)

Internal

  • Temporary-index cleanup reclaims abandoned scratch indexes while owner locks protect active operations, including removal backups. (#4469, thanks @jonah-osmo)
  • Breaking Rust library changes: public types and function signatures changed; downstream crates need to update for 0.82.0.

Install worktrunk 0.82.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/max-sixty/worktrunk/releases/download/v0.82.0/worktrunk-installer.sh | sh && wt config shell install

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/max-sixty/worktrunk/releases/download/v0.82.0/worktrunk-installer.ps1 | iex"; git-wt config shell install

Install prebuilt binaries via Homebrew

brew install worktrunk && wt config shell install

Download worktrunk 0.82.0

Install via Cargo

cargo install worktrunk && wt config shell install

Install via Winget (Windows)

winget install max-sixty.worktrunk && git-wt config shell install

Install via AUR (Arch Linux)

paru worktrunk-bin && wt config shell install

Performance and Compatibility

Worktrunk is written in Rust and distributed as a native command-line application. It does not require a background server or introduce an additional AI runtime.

Its main workload involves Git operations, filesystem management, shell integration, and optional workflow automation. Consequently, its performance depends more on repository size, filesystem behavior, and configured hooks than on AI model processing.

It supports macOS, Linux, and Windows. Installation is available through Homebrew, Cargo, Winget, and several Linux package managers.

Shell integration is available for supported shells, allowing commands such as wt switch to change the current directory directly.

Windows users should note that wt can conflict with the Windows Terminal command alias. The Winget installation provides git-wt as an alternative.

System Requirements

Worktrunk requires:

  • Git installed and accessible through the system PATH.

  • A supported operating system: Windows, macOS, or Linux.

  • A compatible shell for directory-switching integration.

  • A Git repository for worktree operations.

Optional requirements depend on the features being used:

  • Cargo and Rust for building from source.

  • jq for certain integrations and scripts.

  • A compatible AI coding agent for automated agent workflows.

  • A supported filesystem for copy-on-write cache sharing.

Pros and Cons

Pros

  • Simplifies Git worktree creation and management.

  • Designed for parallel AI coding workflows.

  • Supports Claude Code and other command-line agents.

  • Automates development tasks through hooks.

  • Provides interactive worktree navigation.

  • Supports shared build caches.

  • Includes merge, cleanup, and pull request workflows.

  • Written in Rust and open-source.

  • Supports Windows, macOS, and Linux.

Cons

  • Requires familiarity with Git worktrees to use its advanced features effectively.

  • Shell integration requires additional configuration.

  • Copy-on-write cache sharing depends on filesystem compatibility.

  • Some advanced features require external tools.

  • Does not provide AI models or coding agents itself.

How to Install

The easiest installation method on macOS and Linux is Homebrew:

brew install worktrunk
wt config shell install

For installation through Cargo:

cargo install worktrunk
wt config shell install

On Windows, use Winget:

winget install max-sixty.worktrunk
git-wt config shell install

Arch Linux users can install it through Pacman:

sudo pacman -S worktrunk
wt config shell install

After installation, restart the terminal or reload the shell configuration.

Verify the installation with:

wt --help
wt list

To create a new worktree:

wt switch --create feature-test

The official documentation provides additional configuration examples for hooks, aliases, build caches, and parallel AI agent workflows.

Final Verdict

Worktrunk is an excellent utility for developers who frequently work with multiple Git branches, especially those using AI coding agents.

Its biggest advantage is that it makes Git worktrees considerably easier to manage. Features such as automated hooks, shared build caches, interactive navigation, and integrated merge workflows turn what would otherwise be repetitive Git operations into a more organized development process.

It is not an AI coding assistant itself, but it complements tools such as Claude Code and Codex by providing isolated environments for parallel development.

For developers who regularly run multiple coding agents or maintain several features simultaneously, Worktrunk is a practical addition to their development toolkit.

Sources


Worktrunk v0.82.0
Free
Software Informations:
Developer:

Operating System:
Windows / macOS / Linux
Date Added:
2026-11-15T16:07:19.116Z
Categories:

Post a Comment/Report Broken Link: