Worktree
A git worktree is a separate working directory tied to the same repository, often on its own branch, so multiple tasks can run in parallel without stashing changes.
AI tools use worktrees so background agents edit isolated copies while the user keeps working in the main checkout.
What it means
Each worktree has its own branch and file tree; commits in one do not block edits in another until merge, reducing conflict during parallel agent runs.
Why designers should care
When products offer parallel agents or cloud runs, worktrees are the invisible isolation layer—UX should surface which branch/worktree an agent touched and where to review results.
Example
Cursor spins a worktree for a cloud agent on branch fix/a11y-modal; the user stays on main locally and opens a “Review agent branch” link when the job completes.
Common mistakes
- • Parallel agents on one checkout causing merge conflicts with no branch label.
- • Worktree results with no clear path to preview or merge.
- • Assuming non-engineers understand branch names without plain-language summaries.