Skip to main content
Sidekick separates the model from the work. The thread holds the work; the model is a choice you make about how each turn runs. This page explains how that choice is made.

​
Two ways a model gets picked

Auto Route

The default. Sidekick picks a model for each turn from the approved catalog. Routing is handled by Relay.

A specific model

You pick one model from the approved catalog, and every turn uses it until you change it.
Auto Route runs per turn, so a long thread can use different models along the way without you managing that yourself. When you want a specific model, you choose it and it stays until you change it.

​
Admins set the defaults

The set of models available is the approved catalog, controlled by workspace admins. Admins can set the default model choice at three scopes:
  • Organization: the default for everyone in the workspace.
  • Department: the default for a team.
  • Person: the default for an individual.
A default can also be forced, so the chosen model or Auto Route applies and cannot be changed by the person. When a default is not forced, people can pick any model from the approved catalog.

​
Bring your own provider

When the workspace allows it, people can connect their own model provider and use it inside Sidekick. Admins decide whether this is permitted.

​
Changing the model never moves the work

Switching the model, or letting Auto Route switch it, does not take the work out of Sidekick. The thread, its artifacts, and its full history stay exactly where they are. The model is the engine for a turn, not the home for the work.

​
Where to go next

Choosing a model

How to set Auto Route or pick a specific model for a thread.

Govern models

How admins build the approved catalog and set defaults by scope.