User repository on GitHub
- Forks
- 1
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
A Pi coding-agent extension that uses Jev to classify each request and route it to one of three configured models. Supports TypeSafe, Cloudflare AI Gateway, Vercel AI Gateway and OpenRouter backends, with doctor checks, shadow mode and an off-by-default setup.
User repository on GitHub
Repo stats from the GitHub API, cached Oct 2026.
Use Jev to classify requests and route them to the right model for the task. Do not enable this alongside another automatic router. Choose a real provider/model in Pi first, then run: This creates /.pi/agent/typesafe-router.json, initially off, using your selected model for all three routes. Edit the mappings, set TYPESAFEAPIKEY in the environment that launches Pi, and run /reload. Verify your configuration, then enable routing:
Quoted from the project's README. Read the full README.
Watch out
Requires a TypeSafe or gateway API key to classify and route. The README warns against running it alongside another automatic router.
Posts, threads, and videos about this entry from around the web.
Facebook: Intake Router keeps diagnosis out of the answer space at the front desk.
FacebookClinicnotes
YouTube: Jev explained for routing and judging, with a comparison against LLMs.
Hacker News: Vercel on using Jev for defined decisions and GPT-6 Astra when the job also has to write or use tools.
flashbrew4 pointsTypeSafe AI Jev vs. GPT-6 AstraRead the thread on Hacker NewsHacker News: ASTGL replay chose local Laya routing over hosted Jev on one Mac Studio setup.
Jmeg8r15 pointsDoes an open-weight decision model beat a hosted one? Jev vs. LayaRead the thread on Hacker NewsOriginal write-ups on what this entry is for.
Posts from builders shipping with Jev right now.