Top Repos· Jev Integrations· Harness· Last updated 2026-09-21

0xNatoshi / jev-codex-router

“Per-turn model & reasoning routing for Codex, driven by Jev (TypeSafe System One): picks the model, thinking depth and speed mode for every turn.”

Jev Integrations rank #14In Harness #7

• 122Stars
• —Stars Δ / 1d
• —Stars Δ / 7d
• —Stars Δ / 30d
• 14Forks
• 1Watchers

GitHub ↗Official docs ↗Back to ranking

TL;DR

0xNatoshi/jev-codex-router showed up as Jev / System One related work: Agent skill, MCP, or harness that routes work through Jev-style decisions.

The author describes it as: “Per-turn model & reasoning routing for Codex, driven by Jev (TypeSafe System One): picks the model, thinking depth and speed mode for every turn.” That is their claim, not a bench this site ran.

Who it’s for

• Agent / harness authors who need a typed gate, route, or prune step
• Computer-use and browser-loop authors who already have text state from OCR or the a11y tree
• Anyone who needs the unofficial line: jev.pro does not issue keys and is not TypeSafe

What’s inside

Top-level entries on GitHub at generation time: .github, .gitignore, AGENTS.md, BACKTEST.md, CLAUDE.md, LICENSE, README.md, hook, poc, server. Read those before you trust a one-line install.

How to use

1. Clone and follow the author’s Python toolchain. Do not invent a package name.

git clone https://github.com/0xNatoshi/jev-codex-router.git
cd jev-codex-router

2. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
3. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "0xNatoshi/jev-codex-router", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

One typed action per frame

Using 0xNatoshi/jev-codex-router, send Jev a text brief of the current screen and ask for Choice{click, type, wait, give_up}. Do not ask Jev for coordinates or screenshots — it is text-only.

Schema-safe ≠ correct

On a case 0xNatoshi/jev-codex-router gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Does this replace the TypeSafe SDK?

Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.

Are the star chips live?

Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.