Model router CLI
A CLI where you give it a task plus the AI subscriptions you already have, and Jev picks which agent or model should handle it, paired with Herdr to route from one terminal.
- Format
- Article
- Published by
- Community
- Last verified
- Oct 2026
Highlights
- Input is a task plus the list of subscriptions you already pay for, so routing stays inside existing plans.
- Jev returns the agent or model that should pick the task up, acting as a fast judge rather than doing the work.
- It is designed to sit alongside Herdr so a single terminal covers several subscriptions at once.
- The author reports it replaced opening the Claude and Codex apps separately for everyday work.
Watch out
The capture is a launch post, not documentation: it points at a YouTube walkthrough rather than a repository, and no source, install command, question format or API usage is shown in the text. Not stated anywhere: how the subscription list is entered, what a task input looks like, whether the router picks from a fixed agent list or free-text names, how ties or unroutable tasks are handled, whether context limits or per-model cost are accounted for, and whether the routing is confirmed before any work starts. The author's justification is that judgment latency is what makes routing viable, but no latency figure, no accuracy figure and no comparison against routing without Jev is given. A reply agrees that fast judging suits the use case and links to a deeper discussion whose contents are not in the capture. Copy reviewed against the linked page on 2026-10-04.
Questions about this entry
More Jev resources like this
From the Jev guides
Original write-ups on what this entry is for.
From the Jev community
Posts from builders shipping with Jev right now.