Settings

Theme

Show HN: wt – lightweight Git worktree orchestrator for parallel coding agents

3 points by pldpld 2 months ago · 2 comments · 1 min read


I built wt to manage the coordination overhead of running multiple AI coding agents (Claude Code, Codex, etc.) concurrently on the same repository.

The problem: I'd spin up 3-4 agents working on different features simultaneously, then conflict on files, and resolving those conflicts burns agent context. Git worktrees solve the isolation problem but the native CLI is verbose, lacks primitives for managing multiple sessions, and I'd have to manage persistence (folders to store the trees) separately.

wt wraps git worktree in an interface designed for this workflow:

  wt new feature/auth    # creates worktree + spawns subshell
  (wt:feature/auth) $ claude
  exit
  git merge feature/auth
Also integrates with tmux to coordinate agent sessions—wt session watch shows which agents are actively processing vs idle by monitoring pane output buffers.

There's a /do skill for Claude Code that implements issue-driven workflows: /do gh 123 fetches the GitHub issue, creates a worktree with a branch derived from the issue, and populates the agent context with the description.

Written in Rust. Binaries for macOS/Linux.

https://github.com/pld/wt

Blog post with more detail: https://peet.ldee.org/general/2026/01/26/wt-git-worktree-orc...

Hackbraten 2 months ago

Nice! I think multiple worktrees are one of the most-overlooked useful Git features.

  • pldpldOP 2 months ago

    Thank you! It came out of that feeling of I need to use this, but I don't want to have to manage it or have to learn the details more than once. Now I find myself using it daily in my workflow, not having to worry about the extra worktree folders saves enough time to make it worthwhile

Keyboard Shortcuts

j
Next item
k
Previous item
o / Enter
Open selected item
?
Show this help
Esc
Close modal / clear selection