miton
Request beta access

Routing Profiles

How to select and configure model routing profiles based on your task.

Product stage
Development build
Last reviewed
2026-08-27
Successful result
The change is visible in the active project.

What this accomplishes

Select a model routing profile to optimise how prompts are processed among models you have connected. Profiles are defined in packages/pathfinder/data/scoring-weights.ts. Balanced is the default. Cheapest prefers lower cost. There is no keyless profile.

Current availability

This page documents behaviour verified in Miton development builds. Miton is still pre-release and is not publicly downloadable; invited beta users will receive a signed desktop build with automatic updates.

Before you start

  • A Miton development build and an active project.
  • A connected cloud or local model, plus any credentials or local runtime required by this task.

Steps

  1. Locate the roster bar above the chat input field.
  2. Click the Reasoning chip.
  3. Under Auto routing profile, select one of the five profiles.
  4. The system automatically selects the best model from your configured providers to answer your next prompt.

You can also set the default profile, and fine-tune the quality, cost, and speed weights behind it, from Settings → Routing → Routing rules.

Named model groups

Profiles change how candidates are scored. A named model group changes which models may compete. Create groups such as Local only, Cheap coding or Frontier research in Settings, then activate one from the Pool control in the roster.

One group is active globally at a time. A per-session model pin still wins. If every member is disconnected, Miton records the reason and falls back to the wider eligible pool instead of failing the turn.

What success looks like

The roster bar will show the active profile and the specific model selected by the routing engine for your request.

Common failures and recovery

  • Routing to expensive models: Choose Cheapest to minimise cost per turn among connected models.
  • Model switches constantly: This is expected behaviour. The router evaluates the complexity of your prompt and selects the most efficient model on a turn-by-turn basis.
  • A group appears to do nothing: Preferred-model scope disables automatic routing, and a per-session pin takes precedence. Use same-provider or all-providers scope and remove the pin.

Continue with your first project or choose the next task from Docs.