How to Choose and Pin GitHub Copilot Models in VS Code
🔍 WiseChecker

How to Choose and Pin GitHub Copilot Models in VS Code

GitHub Copilot does not have one model setting that controls every VS Code feature. Choose the model for Chat in the chat input, and choose the inline-completion model separately. Pinning a favorite in the model picker keeps it easy to find; it does not freeze a provider’s model version or make generated code reproducible.

Official documentation checked October 14, 2026. Model availability can change with your plan, organization policy and VS Code version.

ADVERTISEMENT

What You Can Select—and What Pinning Means

For a conversation or agent task, look at the model shown in the Chat input. A manual selection is useful when comparing approaches on a small, repeatable task. It is not a guarantee that the same prompt will always generate the same code. Keep your prompt, selected model name, repository revision and test results if you need an auditable comparison.

The current VS Code model documentation distinguishes Chat models, inline chat, inline suggestions and utility tasks. A pinned favorite is simply an entry kept at the top of the picker. It is not a team-wide lock or a commitment that the model will remain available.

Do not add github.copilot.advanced.model on the assumption that it is a supported universal switch. The current official instructions use feature-specific controls. If an older tutorial added that key, remove only that unrecognized entry after backing up your settings; do not erase other Copilot settings.

Choose a Model for Copilot Chat

  1. Open the Chat view in VS Code and check that you are using the intended GitHub account and project.
  2. Open the model picker beside the chat input. Select an available model instead of Auto when you want an explicit choice for the task.
  3. Confirm the displayed model before sending the next prompt. If you are in an Auto session and cannot change it there, start a new chat and select the model before continuing.
  4. To keep a favorite visible, open the picker, hover over that model and use its pin icon. Unpinning changes its position, not your subscription or organization policy.
  5. Test a small, non-sensitive task. Review the proposed changes and run the appropriate tests before accepting a larger edit.

GitHub’s Chat model instructions explain that selecting a Chat model does not select the inline-suggestion model. Models can have different usage costs; consult the usage information for your account rather than assuming every selection costs the same.

ADVERTISEMENT

Choose the Inline-Completion Model Separately

Inline suggestions are the ghost-text completions that appear while you type. They are different from opening an inline chat to request an edit.

  1. Update VS Code and the GitHub Copilot extension through their normal update controls.
  2. Open the Command Palette with Ctrl+Shift+P on Windows/Linux, or Command+Shift+P on macOS.
  3. Search for and run GitHub Copilot: Change Completions Model, then select an option offered to your account.
  4. Open Settings and search for copilot completion. Inspect GitHub > Copilot: Selected Completion Model; an empty field means the default is in use.

An alternative completion model might not be offered. That is not proof of a broken installation. See GitHub’s prerequisites and verification steps.

For inline chat, VS Code also documents inlineChat.defaultModel. Find it in Settings and choose from the values offered by your installed version. It controls inline chat, not ordinary typing completions. Do not copy a guessed model identifier from an unrelated feature.

If Your Selection Is Missing or Changes

  • A model is absent: check the feature you are configuring, your current plan, and your organization’s model policies. A model visible in Chat need not be offered for inline completion.
  • Only Auto or one model appears: use the available option, or ask the administrator about access. A settings file cannot grant an unavailable entitlement.
  • The favorite remains but behavior differs: compare the same task and code revision. Context, instructions and tool access also affect results; do not disable project safety instructions just to force similar output.
  • A model was retired: choose a currently offered replacement and re-run your checks. A saved selection cannot preserve a retired hosted service.

For team consistency, document the intended feature, task, model choice and validation process. Each member should verify their own picker. Share repository instructions and tests, not an unsupported JSON setting presented as a guaranteed model lock.

ADVERTISEMENT

Did this guide solve your problem?