Claude is missing from the list of available models in VS Code.

[joshbrix754-del]

Select Topic Area

Question

Body

Topic Area: Copilot Feature Area
Product: GitHub Copilot

Description
I have an active GitHub Copilot Pro subscription, and Claude models (Sonnet 3.5, 3.7, and 4) are enabled in my GitHub account settings. However, in Visual Studio Code, Claude does not appear in the list of available models.
Currently, I only see the following models available in Copilot Chat:

• GPT-4.1
• GPT-4o
• Gemini 2.0 Flash
• Gemini 2.5 Pro
• o3-mini
• o4-mini
  Claude is missing from the list, and I am unable to select it.
  Troubleshooting Steps Taken
  Verified that I am using the latest version of the GitHub Copilot Chat extension
  Confirmed I am logged in with the correct GitHub account
  Used the /model command in Copilot Chat to check all available models
  Checked GitHub Copilot settings, where Claude is clearly enabled
  System Details
  VS Code version: 1.102.3
  Operating System: Windows 11

[MasteraSnackin]

This is a known issue where Claude models show as enabled in your GitHub account settings but don't actually appear in the VS Code Copilot Chat model selector.

From what I've seen, GitHub rolled out Claude support (Sonnet 3.5, 3.7, and 4) to the web interface and account settings first, but the VS Code Copilot Chat extension hasn't been fully updated to expose these models yet - even though your account technically has access.

You've already done all the right troubleshooting (latest extension, correct account login, /model command, verified settings), so this is just a waiting game at this point. The VS Code extension needs an update from GitHub's side to surface Claude in the model picker.

Keep an eye on Copilot Chat extension updates over the next few weeks. Once they push the update, Claude should just appear in your model list without you needing to change anything on your end.

[wkkkis]

claude missing in copilot chat inside vscode

yeah, this usually isn’t a local vscode bug - it’s almost always entitlement + rollout + org policy weirdness on github’s side.

even if claude is enabled in your github web settings, copilot inside vscode only shows models that:

• your copilot plan is entitled to
• your account is currently flagged for in that environment
• your org / enterprise policies allow
• the vscode extension has picked up via a fresh auth token

---

things that commonly cause this

1) staged rollout / feature flags

github rolls out models gradually.

web UI can say “enabled” while vscode still doesn’t get the flag yet. frustrating but pretty normal for cloud products.

---

2) org or enterprise restrictions

if your account belongs to an org with copilot policies, those override personal settings.

check:

• github → settings → organizations → pick each org → copilot policies
• enterprise policies if you’re under one

this is the #1 cause in practice.

---

3) auth token not refreshed

copilot chat caches entitlements.

try:

• sign out of github in vscode
• reload window
• sign back in
• restart vscode

sounds basic, but it actually fixes a lot.

---

4) extension channel mismatch

if you’re on insiders builds of vscode or copilot, sometimes certain models lag.

worth checking you’re on stable:

• GitHub Copilot Chat
• GitHub Copilot

---

5) regional / backend lag

occasionally the backend just hasn’t propagated your model access yet.

especially if you toggled claude recently in account settings.

---

what i’d do step by step

senior-debugging playbook:

1. fully sign out of github in vscode, restart, re-auth
2. confirm the repo isn’t under an org with copilot restrictions
3. check org/enterprise copilot policies
4. open a brand new personal repo and test there
5. if still missing → open a github support ticket with:
   • vscode version
   • extension versions
   • screenshot of enabled claude on the web
   • exact model list you see

that error is backend-side. nothing in vscode can force it.

---

tldr

• web settings ≠ vscode entitlements
• org / enterprise policy often overrides
• staged rollout is real
• re-auth helps refresh flags
• otherwise it’s support-ticket territory