How worktree appears in this channel's material — and what to do with it here — is limited, so treat this entry as a general orientation plus an honesty note. ### The general meaning A worktree is a git feature that allows more than one working directory to be checked out from a single repository. Each worktree is its own folder with its own checkout, while sharing the repository's underlying object database. In the context of coding agents — the subject of this channel's Coding Agents in Practice material [^717e6970-382c-5199-9605-8fa2c37ec1b2@102] — that property is potentially useful: agents working in separate folders can touch code without stepping on one checkout, which fits the chapter's recurring lesson that the human's job shifts from typing code to planning, orchestrating, and verifying. ### The honesty note In the captured evidence for this glossary entry, worktree is a label only. The channel's material does not include a timestamped passage that defines, demonstrates, or discusses worktrees, and the assigned video does not yield a moment to cite for this term. Nothing in the captured material explains why the term was flagged or how it is concretely used. ### What that means for you - Treat the definition above as the standard git meaning, not as a claim drawn from this channel's captured stream. - Do not treat the term's appearance in the material as evidence that any practitioner here recommends a worktree-based workflow. - If you explore the assigned video [^717e6970-382c-5199-9605-8fa2c37ec1b2@102], explore it for the agents-orchestration themes it actually covers — delegation, orchestration surfaces, multi-agent review, and the limits that still demand human judgment — and note any worktree discussion yourself if you find one.