Worker Routing

---
name: worker-routing
description: Choose a model and effort before dispatching an orq worker through Herdr. Use when preparing an orq dispatch or choosing a bounded Agent subtask.
---

# Worker model and effort

Use the model for the uncertainty in the solution and the effort for the reasoning this task needs. File count and diff size are secondary signals.

## Roles

- **Haiku, scout:** the path is known. Search, locate a symbol, summarize a module, rename, adjust imports, lint, or make a simple config change.
- **Sonnet, default executor:** use low for an obvious fix or one-function test; medium for a normal feature or refactor; high for debugging across several parts of the product.
- **Opus, specialist:** use high for architecture, security, concurrency, data-model or payment decisions; xhigh after a failed attempt or when several hypotheses remain; max as a last resort.

For Codex, use the closest available Luna or Sol profile. Start with Luna for a clear task, raise effort when the work requires more reasoning, and use Sol for a difficult or high-impact decision. Follow any model budget the coordinator gives you.

## Dispatching orq work

An orq dispatch belongs to the Run supplied by the coordinator. orq records the task and dispatch in its own state, and Herdr owns the worker pane and terminal lifecycle.

- Start tracked work with `orq dispatch --run <run> --title <title> --spec-file <file> --model <model> --effort <effort>`. Use `--ticket <number>` when the ticket is the task specification.
- The Agent tool is suitable for bounded exploration or review. Use `orq dispatch` when the work needs durable task identity, coordinator messages, or an explicit completion report.
- A native worker receives its Run, task, and dispatch identity in the environment. It sends a question with `orq worker ask '<question>'`, reports a blocker with `orq worker escalate '<blocker>'`, and records progress with `orq worker heartbeat --phase <phase>`.
- After asking or escalating, read the durable response with `orq worker check`. Finish with `orq worker done --outcome <succeeded|failed> --subject '<summary>' --report-path '<report>'`.
- The owning coordinator acknowledges the completion and releases the worker pane. The worker stops after reporting done.

Choose effort from the task's uncertainty. A small change can still need high effort when the failure is hard to localize; a large mechanical change can use low effort when its path is clear.

## Escalation

Raise one step at a time when a worker fails or reports uncertainty: Haiku → Sonnet low → medium → high → Opus high → xhigh → max. Ask the worker to return the reason and the next suggested step instead of repeating the same attempt.

## Calibrate

Use `orq retro` evidence to adjust the model and effort table. Compare completed work, retries, escalations, failures after completion, and review fixes before changing a default.