JevRouter

What it is

Faster agent decisions. Models, subagents, skills, MCP tools, CLIs and plugins become one candidate set — Jev answers one typed Choice question, JevRouter enforces availability, permissions, risk and confirmation around it.

What the README says it does

• Decision-only by default — nothing executes implicitly; medium/high/critical capabilities require confirmation.
• One call or a plan — route answers one question; plan answers "which capability handles step 1..N" with serial, batch, and decomposed strategies.
• Every surface — models, subagents, Skills, MCP tools, CLIs, DSH plugins share one routing contract.
• Receipts by default — append-only decision/plan files with provenance hashes; what was decided, why, and at what confidence is always auditable.
• Capability trust is explicit — discovered and caller-supplied candidates carry verification status; strict projects can set requireverifiedcandidates to prevent unverified descriptions from being selected.

From the project’s README.

Getting started

From the README:

npx --yes github:BillionsBobby/JevRouter agent start --agent codex

Where the decision sits

JevRouter calls the hosted decision API rather than running its own weights. That keeps the project small and means its behaviour moves whenever the vendor ships a new model version. It also means an API key and a network round trip sit in the path of every decision.

Models it references: Jev.

How active it is

Created 2026-09-18, last pushed 2026-10-04, 467 stars and 29 forks when we read it on 2026-11-02. Everything in this category is weeks old at most, so a stale push date means something different here than it would on a mature project. Check the repository before you depend on it.