BYOK: populate the /model picker from the provider's /models endpoint
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
## Problem
When the CLI runs against a custom provider (`COPILOT_PROVIDER_BASE_URL`), exactly one model can be configured (`COPILOT_MODEL` / `COPILOT_PROVIDER_MODEL_ID`). In-session, `/models` shows only that single configured model — there is no way to browse or switch models without quitting and relaunching with `--model` (which must be guessed, since nothing lists what the provider serves).
## Request
For `COPILOT_PROVIDER_TYPE=openai` (and `azure`), populate the model picker from the provider's standard OpenAI-compatible catalog endpoint:
```
GET {COPILOT_PROVIDER_BASE_URL}/models
```
- Fall back silently to today's single-model behavior when the endpoint 404s or errors.
- `data[].id` is enough for a useful picker; if present, `capabilities.limits` / `supported_endpoints` style metadata could fill the Context column the way the native picker does.
A lighter-weight alternative (or complement): a `COPILOT_PROVIDER_MODELS` env var accepting a comma-separated id list, for providers whose catalog endpoint can't be reached at startup.
## Why it matters
Practically every OpenAI-compatible backend already serves `/models` — Ollama, vLLM, LiteLLM, Azure, and enterprise LLM gateways. We operate such a gateway: it fronts the Copilot API itself (billing stays on the user's Copilot seat) and serves `GET /models` with exactly the models the seat's plan/org policy allows — but the CLI never asks, so enrolled users see a one-entry picker and file "the CLI is broken" reports, while the native CLI right next to it shows the full list.
Observed on v1.0.77 and v1.0.78 (linux-x64 and darwin-arm64).
Contributor guide
Research direction
Trace the CLI's /models picker and custom-provider configuration to find where the current single-model list is assembled. Start by checking the OpenAI and Azure provider paths and their existing error handling. Done means a successful /models response supplies model IDs, while 404s or other errors preserve the current single-model behavior; the optional metadata and environment-variable alternative remain design choices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100