Setup
1
Install the extension
2
Add your API key
Run Opper: Manage API Key from the Command Palette and paste a key from platform.opper.ai. It is stored in VS Code’s
SecretStorage, never in settings.json.3
Pick a model
Open Copilot Chat and choose an Opper model from the picker. Nothing is listed until a key is set — the model list is scoped to it.
What the picker shows
The catalogue is fetched at runtime, so there is nothing to hand-list and nothing to keep in sync. Alongside concrete models such asanthropic/claude-sonnet-4-5, two Opper-specific entries appear:
- Pools — a bare name like
claude-sonnet-4-5that load-balances across every provider serving that model. A pool only advertises a capability every member has. - Dynamic routes — your deployed routing graphs, as
dynamic/<name>. The graph picks the model per request.
opper.euOnly and opper.zdrOnly narrow the list; the gear beside “Opper” in the picker → Choose what to list… turns models, pools and routes on and off individually.
Scoped to your rules
Discovery is filtered server-side by your model access rules, so a model your policy denies is never offered. Those rules are scoped to the API key’s project — the gear menu leads with which project you are on (Opper · <org> · project <name> · N models), which is the quickest way to spot a key pointing somewhere unexpected.
Copilot Business / Enterprise users may need their org admin to enable the “Bring Your Own Language Model Key in VS Code” policy. Individual plans, and no plan at all, are unaffected.
Related
GitHub Copilot CLI
GitHub’s terminal agent, on any Opper model.
Routing graphs
Deploy a route and pick it from the model picker.