Hey fellow devs. If you’ve been deep in the trenches pushing updates to heavy full-stack projects like I have recently with Beatra and CodeShare, you probably rely heavily on AI assistance. But if you opened VS Code around mid-March 2026, you likely encountered a massive workflow killer: Claude Sonnet, Opus, and GPT-5.4 have completely vanished from the GitHub Copilot Chat dropdown.
For paying GitHub Pro and Enterprise users, being stuck with just the default "Auto" model is beyond frustrating. You aren't crazy, and your local setup isn't broken. This is a widespread backend authorization disaster. Let’s dive into the exact GitHub engineering threads, understand the API token routing bug that caused this, and look at the definitive ways to fix it.
The Catalyst: The Student Pack Policy Shift
To understand why your IDE is acting up, we have to look at a major policy update. On March 12, 2026, GitHub officially announced they were restricting premium LLMs (like the Claude 3 family) from the free GitHub Student Developer Pack. The goal was to manage massive compute costs while keeping the base Copilot service free for students.
The intention was clear, but the execution was a mess. When GitHub engineers deployed the permission changes, they inadvertently nuked the telemetry and authorization endpoints for legitimate Pro subscribers using third-party IDEs.
Inside the Engineering Threads: What GitHub Staff is Saying
If you dig into the GitHub Community Discussions, specifically under the rapidly growing outage reports like Discussion #189556 and Issue #189377, you can see the panic and the eventual response from the Copilot Engineering Team.
A GitHub Staff member confirmed the root cause in one of the locked threads:
"We are aware of an ongoing issue where GitHub Pro and Enterprise users are unable to select Claude Sonnet or Opus within the VS Code and JetBrains extensions. The recent rollout deprecating these models for Student accounts caused a temporary desynchronization in how OAuth tokens validate premium entitlements via the api.github.com/copilot_internal/v2/token endpoint. Your Pro access remains intact; the IDE extension is currently failing to retrieve the correct entitlement flags from the server."
In short: Your Pro account has the rights to use Claude Sonnet, but the VS Code Copilot extension is caching an invalid, restricted token that makes it think you are on a basic or student tier.
The Complete Arsenal of Fixes (How to Force Entitlement Sync)
Waiting for GitHub to push a global telemetry fix could take days. Since we need to ship code now, here are the exact, engineer-verified methods to force the authorization servers to recognize your Pro status and flush the bad tokens.
1. The Deep OAuth Token Flush (Highest Success Rate)
Simply reloading the VS Code window does not clear the stale OAuth tokens. You need to force a completely new handshake.
- Click on the Accounts icon (the little person icon) at the bottom-left corner of VS Code.
- Hover over your signed-in GitHub account and explicitly select Sign Out.
- Crucial Step: Close VS Code entirely. Make sure no background processes (like VS Code Server) are running in your Task Manager or Activity Monitor.
- Reopen VS Code, click the Accounts icon again, and select Sign in with GitHub.
- Follow the browser prompt to re-authorize the IDE. Once authenticated, check your Copilot Chat dropdown. The extension will fetch a fresh entitlement payload, and Sonnet should reappear.
2. Hijack the Pre-Release Channel Patch
According to the GitHub engineering team in Issue #189377, hotfixes for API routing bugs are pushed to the pre-release channel before hitting the stable marketplace version.
- Open your VS Code Extensions tab (
Ctrl + Shift + XorCmd + Shift + X). - Search for GitHub Copilot Chat.
- Click the Switch to Pre-Release Version button.
- Wait for the installation to finish, then hit Reload Window. This forces the extension to use the latest token validation logic.
3. Nuke the Local Extension State
If the deep sign-out fails, the Copilot extension might have hard-saved the "missing models" state in its local storage.
- Open the VS Code Command Palette (
Ctrl + Shift + P). - Type
Copilot: Reset Copilotand execute the command. - Next, type
Developer: Reload Window. This clears the extension's local session cache without deleting your settings.
4. The Backend Toggle Trick
If the IDE refuses to cooperate, you can try forcing an update on GitHub's database side to refresh your user flags.
- Navigate to your GitHub Copilot Settings page in your web browser.
- Scroll down to the Editor Policies / Models section.
- Find the Claude Sonnet model toggle. If it says "Enabled", toggle it to "Disabled".
- Wait for about 2 to 3 minutes to let the backend database state settle, then toggle it back to "Enabled".
- Restart your IDE.
The Ultimate Failsafe
If absolutely none of these fixes work for you because of ongoing server-side maintenance, don't let it block your development. This synchronization bug only affects third-party IDE extensions.
You can immediately navigate to the GitHub Copilot Web UI. Log in with your Pro account, and you will find that Claude Sonnet, Opus, and GPT-5.4 are perfectly intact and functional there. Use the web interface to generate, refactor, and debug your code blocks until the VS Code extension receives its final patch.
Have you managed to get your models back using these methods, or are you still stuck with the default model? Drop a comment below, and let's keep track of how GitHub handles this rollout mess. Back to coding! 🚀
