Subject: Copilot Pro+ active subscription but VS Code not syncing premium models — Claude Opus/Sonnet show "Upgrade"

[AllenLiang96]

Select Topic Area

Question

GitHub Feature Area

Actions

Body

Subject: Copilot Pro+ active subscription but VS Code not syncing premium models — Claude Opus/Sonnet show "Upgrade"

Environment

• GitHub Username: AllenLiang96123
• Subscription: Copilot Pro+ ($39.00/month, active, next payment Apr 17, 2026)

• Problem Description

  I am an active paying Copilot Pro+ subscriber. My billing page at github.com/settings/billing confirms the subscription is active — not expired, not in trial, not downgraded.

  However, in VS Code, when I open the model picker in Copilot Chat, Claude Opus 4.6 and Claude Sonnet 4.6 are greyed out and show "Upgrade" instead of being selectable. Other models like Gemini 3.1 Pro and GPT-5.4 are available.

  Likely Trigger

  I previously clicked "Try 30 days free trial" on https://github.com/features/copilot/plans while already being a paying Pro+ subscriber. I believe this action caused a backend state mismatch — my subscription is correctly shown as Pro+ in billing, but the entitlement/token sent to VS Code does not include premium model access.

  Symptoms

  Environment | Claude Opus 4.6 Access | Notes -- | -- | -- github.com (web) | ✅ Works | Can select and use Opus normally VS Code (old machine, local) | ✅ Works | Likely using a cached token from before the issue VS Code (new machine via SSH Remote) | ❌ Shows "Upgrade" | Fresh authentication, premium models not recognized

  What I've Already Tried

  1. ✅ Restarted VS Code multiple times
  2. ✅ Signed out and signed back into GitHub in VS Code repeatedly
  3. ✅ Signed out and signed back into GitHub on the web
  4. ✅ Updated GitHub Copilot and GitHub Copilot Chat extensions to the latest version
  5. ✅ Uninstalled and reinstalled both Copilot extensions
  6. ✅ Cleared system credential manager (Keychain Access / Credential Manager) and re-authenticated
  7. ✅ Cleared Copilot globalStorage cache (github.copilot* folders)
  8. ✅ Confirmed VS Code is up to date (no available updates)
  9. ✅ Confirmed billing page shows active Pro+ subscription ($39/month)
  10. ✅ VPN/network is not the issue (same setup works on old machine)

  Key Observation

  The fact that my old machine still has access (cached token) while a fresh login on a new machine does not strongly suggests that the backend entitlement data sent during new authentication does not correctly reflect my Pro+ subscription. The web interface works because it may read the subscription state differently.

  Screenshots

  VS Code model picker — Claude Opus 4.6 shows "Upgrade":

  

  Billing page — Active Copilot Pro+ subscription confirmed:

  

  Request

  This is not a subscription restoration issue — my Pro+ plan is active and billing is correct. The issue is that VS Code is not receiving the correct entitlement for premium model access during authentication.

  Could the GitHub/Copilot team please:

  1. Investigate the backend entitlement sync for my account (AllenLiang96123)
  2. Fix the token/entitlement so that new VS Code sessions correctly recognize my Pro+ premium model access
  3. Confirm whether clicking "Try 30 days free" on an existing Pro+ account is a known trigger for this issue

  Thank you for your help!

[queenofcorgis]

Hey there! 👋

Thanks for posting in the GitHub Community, @AllenLiang96 ! We're happy you're here. You are more likely to get a useful response if you are posting in the applicable category especially since you've included so many great details like what you've tried that didn't work. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them.

I've gone ahead and moved this to the correct category for you, Copilot Conversations. Good luck!

[frazrajpoot01]

Hi Allen, 👋

First of all, incredible job on the troubleshooting steps. Your hypothesis is almost certainly spot on: clicking the "Try 30 days free" button while on an active Pro+ tier likely created a conflicting entitlement state in GitHub's backend billing database, and the OAuth token being passed to your new VS Code instance is pulling the "trial/basic" scope instead of your active "Pro+" scope.

Since you've already cleared local caches and credential managers, local logouts are just fetching a new token tied to that same broken OAuth grant.

Before waiting on GitHub Staff to manually sync your backend state, there is one "nuclear" token reset method you haven't listed that often forces the backend to recalculate your entitlements: Revoking the VS Code OAuth App entirely from the web.

The "Nuclear" OAuth Reset

By revoking the app authorization completely on GitHub's end, you force the system to generate a brand-new authorization grant from scratch, which often bypasses the cached mismatched state.

1. Go to your GitHub Web Settings: https://github.com/settings/applications
2. Click on the Authorized OAuth Apps tab.
3. Find GitHub for VS Code (and any specific GitHub Copilot apps if listed separately).
4. Click the ... menu next to them and select Revoke.
5. Go back to your new machine's VS Code. You should be forcibly signed out.
6. Restart VS Code, and run the "Sign in to Sync Settings" or Copilot sign-in prompt.
7. Go through the web authorization flow again.

If the models are STILL greyed out:

If Claude Opus 4.6 and Sonnet 4.6 still show "Upgrade" after a forced OAuth revocation, this confirms your account has a hard database desync.

Because this is a public community forum, GitHub staff cannot modify your account state from here. You must open a direct ticket via the GitHub Support Portal.

To bypass the automated support bot immediately, use this exact phrasing in your ticket:

"My account (AllenLiang96123) has an active Copilot Pro+ subscription ($39/mo) but has suffered a backend entitlement state mismatch. I clicked the 30-day trial button by mistake, and now my VS Code token only receives basic Copilot entitlements (Claude Opus/Sonnet are locked). I have fully revoked OAuth access and cleared all local credential caches. Please escalate to the Billing/Accounts team to manually force a sync of my Pro+ entitlements to my IDE token."

Hopefully, the OAuth revocation forces the fix immediately. If not, Support should be able to run a sync script on your account quickly with that information. Let us know if the revoke trick works!

[hardik121121]

One important detail stands out in your setup that hasn't been addressed: your non-working environment is specifically VS Code via SSH Remote, not a standard local install.

This matters because VS Code Remote SSH has a separate authentication context. When you sign into GitHub in VS Code over SSH Remote, the auth token is tied to that remote session. The Copilot extension running in a Remote SSH context authenticates slightly differently than a local VS Code install — it can end up with a different token scope even if your web session shows Pro+.

Quick diagnostic before anything else:

Try opening VS Code locally on the new machine (not via SSH Remote) and sign in fresh. If Claude Opus/Sonnet are available locally but not over SSH Remote, the issue is specifically the Remote SSH auth forwarding, not your subscription entitlement.

If that's the case:

1. On the remote server, check if there's a stale VS Code Server instance with its own credential state: ~/.vscode-server/ may have cached auth that's conflicting
2. Delete ~/.vscode-server/data/User/globalStorage/github.copilot* on the remote machine (not your local machine) and reconnect
3. Re-authenticate Copilot specifically after reconnecting via the Command Palette → GitHub Copilot: Sign in

The OAuth revocation approach in the previous answer is still worth trying, but if the issue is scoped to Remote SSH sessions specifically, the problem is on the server-side credential cache, not your account's backend entitlement.

[yuanyehome]

same issue here

[ysfhtxn]

same issue :(

[RiteshRajpal]

This issue appears to be a classic case of an entitlement desynchronization between GitHub’s billing system and the Copilot authentication service used by VS Code. Since the subscription is active and works correctly on the web, the problem is unlikely related to billing itself, but rather to how the access token is being generated during login. The fact that the old machine still works further supports this, as it is likely using a previously issued token that still contains the correct Pro+ entitlements, while new sessions are receiving a downgraded or incomplete entitlement set.

A likely root cause is the interaction between the existing Pro+ subscription and the “Try 30 days free trial” action. Triggering a trial on an already active paid plan may have caused a state conflict in the backend subscription system, where one service recognizes the Pro+ plan while another service (responsible for issuing Copilot model access permissions) falls back to a lower-tier entitlement. This would explain why only certain premium models like Claude Opus and Sonnet are affected while others remain accessible.

To resolve this, the most effective approach would be to force a full entitlement refresh from GitHub’s side rather than relying only on local fixes. Logging out of all GitHub sessions across devices and revoking OAuth access specifically for VS Code and Copilot from GitHub account settings can sometimes trigger a fresh entitlement sync. Additionally, removing all active Copilot authorizations and re-authenticating after a short waiting period (to allow backend propagation) may help ensure a clean token is issued.

If the issue persists, it strongly indicates a server-side inconsistency that cannot be fixed locally. In such cases, raising a request with GitHub Support is necessary so they can manually resync or reset the account’s Copilot entitlement flags. Providing details such as working vs non-working environments, along with confirmation that the web version works, will help them quickly identify the mismatch.