The three reasoning levels
Every config assigns a model per level. One is enough.
The screen
With no configs, the page shows No configs yet! and a Setup new config button. Each config appears as a card with its name, provider, the model per level, and a Default badge on the current default. Actions: Make default (on non-default configs) and Delete. Available providers below lists every usable provider with its model count and a Requires API key chip. Clicking one opens the config form with that provider preselected.Creating a config
1
Name it and pick a provider
The provider choice unlocks the reasoning-level dropdowns — they stay disabled until the platform knows which models to offer.
2
Connect the provider
- Use saved secret (default) — pick from secrets already in your workspace. See Secrets.
- Add new secret — name it (e.g.
OPENAI_API_KEY) and paste the key. Stored encrypted, used only for that provider.
3
Assign a model per level
Each dropdown lists only that provider’s models; switching provider repopulates all three.At least one is required — saving all three empty returns “Choose a model for at least one reasoning level.”
4
Save it
Tick Make this the default routing config if it should be the default. It’s ticked automatically for your first config.
Changing the default config changes which models subsequent requests use. It doesn’t affect conversations that already ran, and it doesn’t restart any agent.
Model routing vs. agent selection
Two things get called “routing.” This screen controls only the first:
Agent selection decides who handles the request; your routing config decides which model that work runs on.
Related
Routing engine guide
Per-agent configs, pinning, and CLI equivalents.
Routing and flow limits
How the platform picks which agent handles a query.
TokenOps dashboard
What your model choices cost.
Secrets
Where provider keys are stored and rotated.