From input to action
- Send task context with capability and effort questions.
- Normalize native TypeSafe or Gateway answers.
- Map judgments through local model/effort policy before invoking the coding agent.
Implementation details that matter
Provider answer shapes are different
jev-spike.mjs explicitly contrasts native noul/confidence with Gateway boolean/probabilities. Its confidenceOf helper derives a maximum probability only when a native confidence field is absent.
Inspect the supporting source ↗Routing policy remains local
The module combines tier and reasoning-demand results with configured mappings. The example model identifiers and thresholds are a routing policy, not proof that a tier can solve a given repository task.
Inspect the supporting source ↗When to choose it
Use it to make routing choices inspectable and configurable. Measure final task success and total cost, including misroutes, before accepting savings claims.
How to inspect it yourself
Compare the two provider adapters and their confidence/risk readers, then inspect jev-model-router.ts for how each outcome selects model and effort.
Limits of this review
- No Claude Code routing run or cost benchmark was performed.
- Provider SDK changes can alter response metadata; the reviewed commit is fixed.
Primary material used in this analysis