Choosing models
Pick the model behind the copilot, let emma route automatically, or assign a model to each stage of the pipeline.
The copilot is powered by a large language model, and you can choose which one — or let emma pick for you. This page covers the model picker, automatic routing, and per-stage assignment.
In a nutshell:
- Pick a model for the copilot, or leave it on Auto
- Auto lets emma route to an appropriate model for each request
- Per-stage assignment lets you set different models for different parts of the pipeline
The model picker
Open the model picker in the chat to choose the model behind the copilot. The list shows the chat models your account can access. Your choice applies to the copilot's main reasoning; switch it any time.
Which models appear depends on your plan and any keys your company has added.
Auto
Leave the picker on Auto and emma routes each request to a suitable model — a capable model for hard, tool-heavy work, a lighter one for simple turns — so you don't have to think about it. Auto is the default and a good starting point.
Per-stage assignment
Under the hood, emma runs a pipeline: an orchestrator that plans, sub-agents that do tool-heavy work, and background tasks like titling and summarizing conversations. You can assign a model to each stage independently — for example, a top-tier model to orchestrate and a lighter one for background work.
If a chosen stage model becomes unavailable (a removed key, say), emma falls back to a sensible default for that stage and tells you.
What's next
- The copilot — what the model powers
- Bring your own model keys — use your own provider accounts
- Self-hosted inference — run models on your own infrastructure
Last updated on 17 Jul 2026