Worktree
Separate git working copies Orbit creates for parallel work — Coordinator subtasks, Sandbox sessions, Benchmark runs. Auto-managed without manual git commands.
What it is
When Orbit needs isolated parallel work, it creates git worktrees automatically. Coordinator Mode creates one per subtask. Sandbox sessions create one per session. Benchmark Mode creates one per model configuration. When work completes and is promoted/merged/cleaned up, worktrees are removed. You don't manually manage them.
When you would use it
You don't directly use Orbit-created worktrees — they exist behind the scenes for the features that need them. Familiarity with the concept helps when debugging or inspecting state manually.
Common operations
- Running parallel Coordinator subtasks safely
- Isolating sandbox experimentation
- Running benchmark configurations independently
Related terms
Dashed terms are named in the source but do not have a page here yet.
Where this is taught
No learning path uses this term yet. Browse the Learning Atlas for guided sequences through related ideas.