Worktrunk CLI

A git worktree CLI built for running Claude Code and Codex in parallel: the wt command, a plugin, and automation hooks

  • 12,475 ★ on the repository
  • Last commit
CLI

Extended access

Why this level

  • Hooks run arbitrary local commands when worktrees are created and removed
All reasons and checks

max-sixty/worktrunk

Install

Manual install

brew install worktrunk && wt config shell install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Hooks run arbitrary local commands when worktrees are created and removed

This is third-party code. Review the repository files before installing.

What it does

Worktrunk wraps git worktree into three simple commands, so spinning up a separate working copy for each parallel agent task is as easy as making a branch. wt list shows the status of every worktree at once, with icons for active Claude sessions, and hooks (post-start, pre-commit, post-merge and others) automate local steps like installing dependencies or copying .env when a new worktree is created. The Claude Code plugin adds guidance on configuring hooks and LLM commit message generation right inside the agent session.

Who it is for. For developers running several parallel Claude Code or Codex sessions on the same repo who are tired of managing worktrees by hand.

Good fit when

  • You need to run several agent tasks in parallel without conflicts in a single working copy
  • You want to automatically copy .env, install dependencies, or start a dev server when a new worktree is created
  • You need to quickly see which worktrees currently have an active agent session

Not a fit when

  • You only work on one task at a time and do not need worktrees
  • The project does not use git

Example request

Create a new feature-auth worktree from main and switch into it

Limitations

Requires installing the wt binary and setting up shell integration for directory changes. LLM commit message generation requires configuring your own model provider.

How to disable. Remove the plugin via /plugin in Claude Code and uninstall the binary: brew uninstall worktrunk.

FAQ

How is this different from plain git worktree?

Worktrunk collapses the usual git worktree add/remove/switch combinations into three simple commands and adds hooks, a status table, and copy-on-write build cache handling.

Do I need the Claude Code plugin if I only use the CLI?

No, wt works as a standalone CLI; the plugin only adds guidance and active-session indicators inside the agent's context.

Discussion

No questions or reviews yet.

CLI tools

A Rust CLI and TUI: agents in containers, parallel tabs, TOML workflows from issue to PR and a scheduled agent squad

CLIBroad access73Repository stars

A skill that splits changes into logical Conventional Commits and safely handles branches, pushes and pull requests.

SkillExtended access105Repository stars

A CLI that gives every feature its own Git worktree and environment so agents and people work in parallel without colliding

CLIExtended access89Repository stars

Tern terminal plugin: one panel for every branch with worktrees, agents, PRs and tickets, plus a Visualize PR skill.

PluginExtended access107Repository stars

A skill and plugin for Git and GitHub: branches, Conventional Commits and a pull request path to a green merge.

SkillExtended access59Repository stars

Grove opens a Zellij session with one tab per git worktree, each with LazyGit, a shell and an AI agent.

CLIExtended access81Repository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialRepository starsMain difference
Worktrunk (this card)no12,475
dotaino1,163eleven skills for Claude Code and Codex
Weaveno1,356a Git merge driver and MCP server that compares functions and classes
Foremergeno436a CLI and MCP server where parallel coding agents declare what they

README in short

The README presents Worktrunk as a git worktree CLI designed for running AI agents like Claude Code and Codex in parallel. Three core commands replace the usual git worktree add/remove/switch juggling, with hooks at various points in a worktree's lifecycle and a copy-on-write build cache. Install via Homebrew, Cargo, Winget, pacman or conda-forge. It also documents a Claude Code plugin that adds active-session indicators to wt list and guidance for configuring hooks and LLM commit messages. MIT or Apache-2.0 licensed.

README badge

Original SKILL.md

---
name: worktrunk
description: Guidance for Worktrunk (the `wt` CLI) — git worktree management, hooks, and config. Load when working out which worktree a `wt` command will act on, or reaching for the global `-C <path>` to target one; editing .config/wt.toml or ~/.config/worktrunk/config.toml; adding, modifying, or debugging hooks (post-merge, post-start, pre-commit, pre-merge, post-switch, etc.); configuring commit message generation or command aliases; or troubleshooting wt behavior. Also answers general worktrunk/wt questions.
license: MIT OR Apache-2.0
compatibility: Requires the `wt` CLI (https://worktrunk.dev)
---

# Worktrunk

Help users work with Worktrunk, a CLI tool for managing git worktrees.

Report a problem