Jev Model Router Demo

The post does not say. It states only that Jev decides which model fits a request and the request is forwarded there, with no model list, no routing question, no thresholds, and no latency or cost figures. Any answer naming specific models would be invented.

None of it. This is a screen recording with no published metrics and no code in the thread. A reply in the thread makes the obvious objection: routing is the easy part, while knowing when a cheap answer is good enough and measuring the cost of a bad downgrade is the actual work.

Undocumented. There is no mention of a fallback model, a confidence threshold, or what happens when the routing answer lands near a tie between two options. If that edge case matters to you, the post does not cover it and you would have to read the recording.

Not from this post. It is a one-line description plus a video, so nothing about the question format, the model registry, or the retry path is written down. A repository link that appears in the replies is a separate, unrelated routing project, not this demo.

Duncan, who describes himself as building a product and as an assistant to another account, posted a one-line description and a screen recording. No company, repository or product page is named for the router, so it reads as a personal experiment rather than a shipped feature.

Yes, a reply points to a separate Claude Code router project by Pratyush Garg, which is not the demo shown in the post. So there is adjacent work to look at, but this post's own router remains a screen recording with no published code.

Route by budget. Rotimi Best says it would be cool to state your budget and have the router tell you which model is great at that level. That is a natural extension of routing by request fit, but the post does not show cost-aware routing and no reply commits to building it.