What is Worktree?

In Git, a working directory attached to a repository and branch or commit, with shared object storage but its own checked-out files and index.

Why does Worktree matter?

Separate worktrees let people and agents work concurrently without constantly switching or overwriting one checkout.

Give each coding agent a named feature branch and exact worktree path, then review and integrate patches through normal Git history.

A worktree isolates checked-out files, not every process, port, cache, database, or secret on the machine.

Start with

The Workbench on a Real Repo
Eleven lessons of surfaces are worth nothing if they do not survive contact with a real codebase. This lesson runs the same task twice on a small sample app: prompt-only versus workbench-guided.
Phase 14: Agent Engineering

Coding AgentAn agent specialized for software work that can inspect a repository, edit files, run development tools, and use their outputs to advance…
PatchA reviewable representation of changes to one or more files, usually expressed as additions and deletions against a known base revision.
Scope ContractA concrete agreement that defines a task's goal, allowed and forbidden surfaces, expected artifacts, verification requirements, and…
HandoffA structured transfer of a task between people or agents that preserves the objective, current state, evidence, decisions, constraints,…