Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
Improve clarity of git worktree context and UX explanation
Maximilian Roos342090279aec
diff --git a/README.md b/README.mdindex 8eb5fa7f3..57df6846b 100644--- a/README.md+++ b/README.md@@ -25,11 +25,13 @@ Here's a quick demo:## Context: git worktrees-AI agents like Claude and Codex can increasingly handle longer tasks without supervision, and it's very practical to run several in parallel. On a single file tree, they step on each other's uncommitted changes.+AI agents like Claude and Codex can increasingly handle longer tasks without+supervision, and it's very practical to run several in parallel. Git worktrees+are a great primitive for giving each agent its own working directory, avoiding+agents stepping on each other's changes.-Git worktrees are a great primitive for this: multiple working directories sharing one `.git`.--But the UX is clunky: `git worktree add -b feature ../repo.feature`, then `cd ../repo.feature`, then `git worktree remove ../repo.feature`.+But the git worktree UX is clunky. Even something as simple as "start a new worktree" is complicated:+`git worktree add -b feature ../repo.feature`, then `cd ../repo.feature`.## What Worktrunk addsdiff --git a/docs/content/why-worktrunk.md b/docs/content/why-worktrunk.mdindex fc98f8214..5a81b416f 100644--- a/docs/content/why-worktrunk.md+++ b/docs/content/why-worktrunk.md@@ -14,11 +14,13 @@ Here's a quick demo:## Context: git worktrees-AI agents like Claude and Codex can increasingly handle longer tasks without supervision, and it's very practical to run several in parallel. On a single file tree, they step on each other's uncommitted changes.+AI agents like Claude and Codex can increasingly handle longer tasks without+supervision, and it's very practical to run several in parallel. Git worktrees+are a great primitive for giving each agent its own working directory, avoiding+agents stepping on each other's changes.-Git worktrees are a great primitive for this: multiple working directories sharing one `.git`.--But the UX is clunky: `git worktree add -b feature ../repo.feature`, then `cd ../repo.feature`, then `git worktree remove ../repo.feature`.+But the git worktree UX is clunky. Even something as simple as "start a new worktree" is complicated:+`git worktree add -b feature ../repo.feature`, then `cd ../repo.feature`.## What Worktrunk adds