$ cat ~/map/pi-jev-router.md

pi-jev-router

Task-boundary model routing powered by TypeSafe Jev — new tasks get re-tiered, continuations keep their model.

extensions✓ Sep 21

Run pi install git:github.com/win4r/pi-jev-router, restart pi, then run /route init and edit the generated .pi/jev-router.json before /route reload and /route doctor. Requires Node.js 22.19+ and pi 0.84.2-0.86.x.

## TL;DR

Task-boundary model routing for pi powered by TypeSafe Jev: new tasks get re-tiered across quick, general, and frontier models while continuations keep their current model, with shadow mode by default and Jev network calls off until enabled.

## Key points

• $Routing is boundary-aware: only a first task or /route new triggers reclassification; continuations, resumed sessions, and same-task follow-ups keep the current model, and an ambiguous continuation without a briefing never calls Jev.
• $Tiers are your policy, not Jev's verdict: you assign models to quick, general, or frontier tiers in .pi/jev-router.json; the router then filters by tool support, reasoning ability, image needs, and context and output headroom before weighing price and observed cache reads.
• $Shadow first: the default mode only shows suggestions; /route preview prints a proposal without executing it, /route explain dissects the last real decision, and /route auto turns automatic switching on explicitly.
• $Jev sees the minimum: the task text, an optional /route brief capped at 6000 UTF-8 bytes and kept in-process, plus flags for images, tool needs, the floor tier, a new task, and last-run failure — never history bodies, tool outputs, system prompts, image contents, the model catalog, or prices.
• $Failover is plumbed for reliability: a persisted circuit breaker, inter-process locks, trial leases, and late-result checks guard switches, and the router pauses auto-switching when it detects /bifrost.

## FAQ

## References

• README ↗
• Design and boundaries ↗

Last updated: Sep 21, 2026