Worktrees

Where implementation happens

An execution request covers worktree preparation. Default branches are cc/<plan-id>/<repository-id>, under .worktrees/<plan-id>/<repository-id>. A person may instead request direct work in a bound checkout, preserving its branch and existing work.

The starting point is this machine's base branch unless an explicit start or dependency requires another reference. No fetch happens implicitly. Reusing a branch does not reset it.

Environment reuse is not setup

Preparation can clone ignored dependencies and environment files using native copy-on-write, with independent copies as fallback. It reports reused, skipped, and mismatched entries without exposing contents. The agent still follows repository setup instructions and runs checks.

Preserve working copies

Git's inventory is authoritative; the local plan association is a convenience. Inspect actual branches and diffs on resume. Completion removes neither worktrees nor branches. Removal preserves dirty, untracked, and ignored files unless disposal was explicitly authorized.

See worktree commands.