Documentation menu
Documentation

Choosing models

Winskel picks models by default. You can name the model you want, and more controls are in development.

Autopilot by default

Give Winskel an objective without naming a model and it chooses one for each part of the work, only among the models your accounts can run. You do not need to configure anything.

Name a model

Write the model's full name, such as Opus 5.5 or GPT-5.6 Sol, in the objective. Winskel uses it instead of choosing. Nicknames are not guessed.

  • If the objective stays one task, that task runs on the named model
  • If the work splits, Winskel uses the named model for the part it fits and stops if it cannot tell which part you meant
  • If your account cannot run the named model, Winskel stops and explains instead of swapping in another

Default model

During setup you choose the model Winskel falls back to when its routing rules do not settle the choice.

In development

  • Allowed model pools and models to never use
  • Preferred models by kind of work, and a quality, speed, or cost preference
  • Custom orchestration: your own workflow, such as Claude plans, Codex implements, Claude reviews
  • A default that each repository can inherit or override
  • Rating a routing choice and routing that learns from your history