work-tree

---

Why Work

Working on three branches in three repos with three Claude Code instances is a productivity superpower — if you can keep the cognitive overhead under control. Without tooling, you end up juggling terminals, losing track of which session is in which directory, and rebuilding mental context every time you switch.

Work is the missing layer between git worktree and your AI assistant. Every branch gets a real, isolated checkout. Every checkout gets its own Claude Code session, persisted across resumes. Every session is visible — alongside its PR status, assigned Jira issues, and pending tasks — in a single dashboard.

Without Work	With Work
cd ../some/path && git checkout -b feature/x && cp .env.local . every time	work tree api feature/x — worktree created, dev settings copied, Claude launched
Three terminals, three editors, three lost contexts	One TUI: sessions, PRs, Jira, tasks — keyboard-driven, mouse-aware
"Which directory was that branch in again?"	work resume — recent sessions sorted by last access, one keystroke to re-enter
Multi-repo features = multiple git worktree add invocations and a hand-merged CLAUDE.md	work tree mygroup feature/x — every repo cloned in lockstep, combined CLAUDE.md generated automatically
Stale worktrees pile up after PRs merge	work prune (interactive) / work sync (one-shot) — remove worktrees whose branches landed on main
Jira ticket → branch name → worktree → Claude prompt = manual every time	Select a Jira issue in the dash → branch slug auto-generated → worktree created → planning prompt sent to Claude
Same chore (npm test, rebase) in five worktrees, one terminal at a time	work run --all npm test / work broadcast --all "rebase onto main" — fan out across the fleet
Diffs and reviews scattered across terminals and editor tabs	wd / work web — every diff and review in one browser, comments routed back to the live AI session

---

Quick Start

# 1. Install (Node 18+, Git required)

# Option A — Homebrew (macOS / Linux)
brew install moberghr/work-tree/work    # provides `work` and `wd`

# Option B — from source
git clone https://github.com/moberghr/cli-work-tree-manager work
cd work
npm install
npm run build
npm link

# 2. First-time setup — interactive
work init

# 3. Create a worktree and launch your AI tool
work tree api feature/login

# 4. Open the dashboard (terminal TUI, or `work web` for the browser)
work dash

work init walks you through the worktrees root, your repo aliases, your AI command, and tab-completion installation. Everything else is one keystroke away from the dashboard.

Prerequisites

Tool	Required	Used for
Node.js 18+	yes	Runtime
Git	yes	Worktree operations
Claude Code CLI	recommended	Default AI tool auto-launched on work tree; group CLAUDE.md generation. Any other CLI works too — set aiCommand in config.
GitHub CLI (gh)	optional	PR pane in the dashboard / work web
Atlassian CLI (acli)	optional	Jira pane in the dashboard / work web

---

Commands