Skip to content

Model selector

Open in product: preshos.com/agent-ops/model-selector

The model selector names which model a session reasons with, and how hard it reasons: model plus reasoning effort apply to the run. It changes how the agent thinks through the work — not what the agent is allowed to touch. Environment policy, tool grants, and approval gates apply the same regardless of the model picked.

  • Reasoning style and strength for the task at hand: harder judgment work earns the stronger model, routine reads do not need it.
  • Cost and latency posture of the session. Stronger models cost more per step; long sessions multiply the difference.
  • Nothing about scope. A different model in the same environment sees the same systems under the same policy.
Model selector: available models with capability and status per row
  • The environment tool list. If a system is not listed there, no model reaches it.
  • Approval gates. Risky actions pause for a human decision under every model.
  • The recorded outcome. Model, runs, and tokens stay on the record either way.

A speed control is transmitted with the run but currently has no effect on it. Judge speed by the session in front of you, not the setting — and treat the product UI as the source of truth if its behavior changes.

  • Default to the agent’s configured model. It was picked for that workload; overrides need a reason.
  • Change the model for the work, not the mood. A stuck session usually needs rescoping, not a stronger model.
  • When no model looks right or the picker is empty, ask the tenant admin. Available models come from the model registry.