Let OpenWork pick the right model for every prompt, from the AI Gateway models you choose.
Auto Model Routing lets members choose Auto instead of a specific model. For every prompt, OpenWork picks one of the models you listed, based on what the prompt asks for. Each model runs at the thinking level you chose for it. Quick questions go to a fast, inexpensive model. Hard coding, planning or debugging goes to your strongest model with more thinking. Anything else goes to your default model.You set it up once for the organization in OpenWork Cloud under AI Gateway → Auto Router. Members don’t configure anything: Auto appears at the top of their model picker.
Auto Model Routing is rolling out on OpenWork Cloud. If you don’t see the Auto Router tab, ask OpenWork to turn it on for your organization.
Lower cost without thinking about it. Members no longer run every small question through the most expensive model.
Better answers on hard work. Difficult prompts get your strongest model and more thinking, even when a member forgot to switch.
One choice for members. People who don’t know the difference between models pick Auto and get a sensible model each time.
Same rules as any other model. Auto only uses models already in your AI Gateway. Access, limits, usage counting and costs work exactly as if the member had picked the model themselves.
Auto can only use models that are already in your AI Gateway, in an active model group. If you haven’t yet, add a provider and its models first.
2
Turn on the Auto Router and choose a default model
Open AI Gateway → Auto Router, the tab right after AI Providers, and select Turn on.
Before it is turned on, the Auto Router tab explains what it does.
You start by choosing the default model. Auto uses it whenever no other model’s description matches the prompt, and whenever it can’t decide. Its description is fixed: “Use this model when no other prompts and models match the input”.
Model: choose one of your AI Gateway models.
Thinking: choose the one thinking level this model always runs at. Only the levels the model supports are shown. Default uses the model’s own setting.
Select Turn on.
The default model has a fixed description; you choose the model and its thinking level.
3
Add more models and describe when to use them
Select Add model for each other model you want Auto to use:
Use when: describe, in plain words, the prompts this model should get. For example “Everyday questions, small edits and short answers”, or “Hard coding tasks, architecture, debugging complex failures”.
Model: choose one of your AI Gateway models.
Thinking: choose the thinking level this model runs at.
Select Save route. Two or three routes with clearly different descriptions usually work best: a fast model for everyday work, a strong model for hard work, and optionally a model for a specialty such as reading images or long documents.
Each route leads with when to use it; the default model is always first.
Write descriptions that separate the routes from each other. “Simple questions” and “Hard, multi-step coding and planning” route better than two descriptions that both mention coding.
Members whose organization has the Auto Router turned on, and who have access to at least one of its models, see Auto as the first option in the desktop model picker. Auto manages thinking itself, so the effort control shows Managed by Auto.
Auto is the first option in the model picker.
Each reply shows which model answered it and at which thinking level, next to the reply’s time.
Each Auto reply names the model and thinking level that answered it.
Auto Model Routing runs inside the AI Gateway. Every Auto request still uses the member’s own AI Gateway key, as described in How requests flow.
Only your models, only theirs. The gateway starts from your routes and drops any model the member doesn’t have access to.
One decision per task. At the start of each task (when the member sends a message), the gateway asks Jev, a fast routing model from TypeSafe, to choose one route. The route runs at the thinking level you set for it. Jev sees the member’s latest message and a short excerpt of the conversation, your route descriptions and model names. It never sees your provider ids or keys. The decision usually takes well under a second.
Consistent within a task. The steps that follow while the agent works on the task (tool results, follow-up calls) keep the same model and thinking level, so the model’s context and prompt cache stay intact.
Sent like a normal request. The gateway forwards the request to the chosen provider exactly as if the member had picked that model: the same access checks, limits, usage counting and costs apply, and the request log records the real model. Auto translates the request for the provider when needed, so Anthropic, OpenAI, Google Gemini, Amazon Bedrock, Azure OpenAI and OpenAI-compatible providers can all be mixed.
A safe fallback. If Jev can’t answer in time, Auto uses your default model.
Each route runs at one thinking level you choose. More thinking gives better answers to hard problems but is slower and uses more tokens, so pair fast, low-thinking routes with everyday work and high-thinking routes with hard work.
Select Turn off on the Auto Router tab. Auto disappears from members’ model pickers the next time their app syncs with your organization, and requests already set to Auto stop routing. Your routes, including the default model, are kept, so turning it on again brings them back.
Auto Model Routing is offered on OpenWork Cloud first. Where it is available on a self-hosted install, give the AI Gateway a TypeSafe API key through the Helm chart’s secret.values.typesafeApiKey (or the TYPESAFE_API_KEY key in your existing Secret). Without a key, Auto is off: the Auto Router tab explains how to add the key, and members don’t see Auto. See the chart’s README for details.
