User repository on GitHub
Route each Codex turn to the cheapest model that can handle it, judged by TypeSafe Jev.
- Forks
- 2
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
A model router for the Codex CLI: on every user turn Jev judges how hard the task is and a YAML policy picks one of three lanes — flash, craft or forge — so premium quota goes to the prompts that need it.
User repository on GitHub
Route each Codex turn to the cheapest model that can handle it, judged by TypeSafe Jev.
Repo stats from the GitHub API, cached Oct 2026.
Watch out
MIT, and Codex-only: it runs a loopback Responses proxy and is not an MCP server, so Codex starts through its own command and another model pinned in /model pauses routing. Live routing needs a TYPESAFE_API_KEY; without one, or if Jev times out, it fail-opens to the craft lane and marks the decision degraded.
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 NewsPosts from builders shipping with Jev right now.