The dialog now explains what it asks about: the skill's description (from its SKILL.md frontmatter, five YAML forms, first sentence, cleaned), the agent's description (from agent.offer), the phase's new 'about' line in routing.json, and the real model id and effort the next step runs on. Options Later / Keep / Change; Change asks the model (fable, opus, sonnet, haiku with their tier role), then the effort among those the phases of that model offer, then the scope; the pair maps to an existing phase (rows stay phase names; the row's current phase wins a tie; same phase = Keep). A main-loop phase (T3) is Later / Keep only. A main-row change toasts the real decision and the /route switch hint when the pick is a downgrade. Descriptions pass a hardened read (name allowlist, stat kind, size cap) and clean(). Kit suite 190 → 232; W3-A dialog tests migrated. Contract .claude/tasks/contracts/2026-10-11-model-router-w3b-dialog-1240.md, plan r3: 3 lenses (2 BLOCKERs: inline rows, phase edits) + 1 confirmation, feater + 2 rounds, GATE 0 MET, verifier CONFORME (3rd pass), security PASS.
3.0 KiB
Route doctrine — phase-level model and effort on the main loop (BDR-107)
Shared include, companion of lib/model-gate.md: the gate fixes WHICH model
reflects, the model-router mod (mods/model-router) fixes HOW HARD each
phase thinks. Rungs: low (fix a line, run a script) · medium (day-to-day) ·
high (refactor, resisting bug) · xhigh (architecture, audit before
validation) · max (stuck error, judged need).
The tool
mcp__model-router__route (params phase | effort | clear). It is a
deferred tool: when not loaded, run
ToolSearch("select:mcp__model-router__route") once per session. A route
applies from the next request on, paired with
another tool call or not (pairing only saves a request). The answer always
names the id and effort main runs on. A skill with a row routes itself on
load; a skill without one changes nothing, the last ROWED skill wins.
Wiring points
- Dispatch span starts →
route(phase="orchestrate"), sent with the dispatch. - Reflection resumes (challenge synthesis, verdict, plan revision) →
route(phase="reflect")or"plan"per the skill's own level; the line before everylib/challenge-plan.mdcall. - Bookkeeping tail (memory commit, doc commit) →
route(phase="apply"). - Escalation →
route(phase="escalate"): verify-secure loop caps and ship-feature STEP 4b. Not automatic: the challenge fail-safe and "gone WRONG → STOP"; their STOP text names the levers below. - Built-in judgment dispatch (
general-purposemodel="opus",model: "fable"skill-runners) → expliciteffort=on the Agent call (xhighfor opus reviewers,highfor fable runners). A main route never reaches a child. Typed agents run on their row, never on a shift. - After a prose gate that ends the turn, the resumed reflection phase starts with its own route call.
Run slot and levers
A best-tier skill row survives the end of the turn (a run spans prose
gates); /route clear, /route off and a user /model drop it. Levers for a
relaunch: ultrathink in the prompt (turn floor) or /route effort=max
(sticky, /route clear after).
Builtin /effort is NOT a lever inside a run: rows and routes outrank it.
Limits
- A skill typed while a background agent is live routes only through the typed marker (unverified live 2026-10-10).
- Headless (
-p, SDK) runs the hooks, so routing works there too. - Mod off: typed agents fall back to their
model:/effort:frontmatter. - First use of a row asks once, with context (Later, Keep or Change: model,
then effort, then Everywhere or this project only); the answer is kept in
mods/model-router/routing.json./route pendinglists what is still unconfirmed,/route ask off|ontoggles the dialog.
Measure the split any time: python3 ~/.claude/lib/effort-audit.py
(thinking/output/cache tokens per scope, model and effort).
Never
- A route inside a dispatched agent: its row rules there.
- Max is for diagnosis, not for retrying the same fix harder.