duet-agent Jev Routing
duet-agent uses a Jev-backed routing table to select models for agent work.
Added to Jevfast
How it uses Jev
At a turn start or routing milestone, the router supplies Jev with the virtual tier, trigger, image presence, current model and route, and bounded hints from the previous turn and latest agent step. Jev returns a typed `choice` among that tier’s route names, with probabilities when available; the router resolves the choice to a concrete model and effort, then applies the change to the agent.
What Jev decides
Illustrative Jev decisionExample answers · not a recorded Jev response · Source ↗
Question 1 · route
YOUR APP
INSTRUCTION
Choose the frontier-tier route whose description best matches the agent’s next work.
STATE
Frontier tier, routing trigger, image presence, current target, previous-turn hint, and current request or latest step.
JEV · CHOICE
- visual
- plan
- implement
- writing
- general
App workflow
- Choose a virtual tier
The routing table defines routes and descriptions; its classifier target can select the evaluation path with `typesafe-ai/jev`.
- Build the request
Supply trigger, tier, image presence, current target, previous-turn hint, and current request or latest step delta; route descriptions become the choice criteria.
- Read the choice
Take `answers.route.choice` and its returned probability distribution, if present, and reject route names outside the tier.
- Resolve and switch
Resolve the route to a concrete model and effort, account for image fallback, then apply the target to the agent and emit a router-switch event.
Why it is interesting
It asks Jev to choose a policy-defined route while keeping concrete model resolution, image fallback, and cache-aware switching in deterministic application code.