For developers

Routing

Every request gets the right model for each part of it, careful for deep research, quick for errands, and an answer still comes when a model is down.

FreeMac

Choose an example to copy it, then try it in Jevie.

Use itHow it worksLimitsWhere it's kept

Use it

• the 3 best-reviewed robot vacuums under $400Planned and written by a balanced model, its pages read five at a time
• how far is Austin from DallasAnswered at once, no planning needed
• the latest SwiftTerm release and what changedGitHub asked beside the web search
• my next meetingdid anyone email me about an invoiceYour calendar and mail searched directly, not through their websites
• add a cube in BlenderDone through your coding agent's Blender tools instead of clicks on its canvas
• open your files, then ROUTING.mdYour own choice of model class for a kind of work

How it works

Jevie reads what each request is (what kind of work, how deep, whether money is at stake) and picks a careful, balanced or quick model for planning, reading pages and writing, from the models this Mac can reach. Over time it learns from your own runs which model does each kind of work best.

No answer waits on one model being up: a silent or failing model is passed over in about a second, and the line under the answer names the model that wrote it. A run's record shows which model did each call, with its time and cost.

Limits

• To be routed, a request's first 600 characters and what is in front are sent to Typesafe; without your own key, requests go the way they did before routing.
• On the phone with the Mac away and Jevie Cloud unreachable, no answer comes.
• Apps reached through a coding agent's tools are a fixed list, such as Blender, Figma and Photoshop.

Where it's kept

jevie/kernel/route/ (facets.mjs the fourteen questions, policy.mjs the classes, registry.mjs the providers, stats.mjs what runs taught, agents.mjs the agents' MCP servers), called from jevie/entry/ask.mjs. Your ~/.jevie/self/ROUTING.md, what runs taught in ~/.jevie/route-stats.jsonl, models.dev kept in ~/.jevie/cache/models-dev.json, the reachable providers in ~/.jevie/cache/route-candidates.json. More: docs/routing.md.

In Jevie, help routing answers from this page as you type.

Related

Updated 23 October 2026 · Something wrong or missing? Tell us