Worker Orchestration
Goal
Route and compose bounded child OpenCode workers through one Unix abstraction.
Workflow
- Determine task, role, mutation authority, budget, and required independence.
- Resolve logical models through
opencode-worker-resolve-model; never derive model IDs from prose labels. - Pipe complete prompts into
opencode-workerand consume stdout as the result. - Keep diagnostics and usage metadata on stderr. Do not parse terminal escapes.
- Bound concurrency, retries, elapsed delay, iterations, and total budget.
- Use isolated linked worktrees for mutating lanes. Read-only lanes may share a checkout; never run parallel mutation in one worktree.
- Reconcile independent results in the parent and verify claims against source.
Use independent models or perspectives for high-value review when budget permits. Server attachment is optional optimization; standalone operation remains correct.