Copilot Pro subscription. #183951
Replies: 5 comments 2 replies
-
|
Hey, this usually happens when Copilot Pro is active on the billing side but not fully synced to Copilot Chat yet. That 402 quota_exceeded with sku: free_limited_copilot means Copilot Chat is still treating the account like it’s on the free tier, even though Pro shows as active. Common reasons: There’s a backend sync delay after upgrading to Copilot Pro The VS Code Copilot extension is using an old auth session Sometimes the Copilot Chat quota gets misattached on GitHub’s side Things to try first: Sign out of GitHub in VS Code, then sign back in Reload VS Code and make sure the Copilot extension is up to date Check that you’re logged into the same GitHub account that has Copilot Pro If it still happens after that, it’s not a local issue. GitHub Support has to fix the quota attachment on their side. So yeah, the subscription is active, but Copilot Chat is temporarily confused |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I have an active Copilot Pro subscription on my GitHub account, and the billing page shows it as active. However, when I use Copilot Chat, I keep getting this error: This is happening in multiple VS Code sessions, so it doesn’t seem to be a local issue. It looks like my account is still being treated as a free Copilot account even though Pro is active. Could you please check if my Copilot Chat quota is correctly linked to my account? Thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
|
I have an active GitHub Copilot Pro+ subscription on my account (username: Selin611). Proofs from my side: GitHub Billing → Copilot Pro+ is active GitHub Settings → Copilot features are enabled VS Code Copilot extension is authenticated and working for code completion Copilot backend logs confirm valid token and successful requests (gpt-4.1-copilot) However, Copilot Chat is consistently failing with the following error: 402 quota_exceeded This happens across: multiple VS Code sessions restarts re-logins extension reloads So this does not appear to be a local or client-side issue. Based on the behavior and the error SKU, it looks like Copilot Chat is still treating my account as “free_limited_copilot”, even though Copilot Pro+ is active on the billing side. This strongly suggests a server-side quota / entitlement mismatch, where the Copilot Chat quota is not correctly attached to my Pro+ subscription. Other users are reporting the same pattern: Pro active in billing Copilot Chat returning free_limited_copilot Issue resolved only after GitHub backend intervention Request: I’m happy to provide: screenshots of billing and Copilot settings VS Code Copilot logs timestamps of failing requests Thank you in advance — this appears to be a backend synchronization issue rather than a user configuration problem. |
Beta Was this translation helpful? Give feedback.
-
|
This usually happens when Copilot Chat is authenticated under a different GitHub account than the one with the active Copilot Pro subscription. Please try the following: In VS Code, open the Command Palette → Restart VS Code Sign back in and make sure you select the same GitHub account that shows Copilot Pro active in billing. Confirm Copilot is enabled: VS Code → Extensions → GitHub Copilot → Enabled Sign-in status shows your Pro account If the issue persists: Check whether your Pro subscription is personal vs organization-based Ensure you are not signed into GitHub Enterprise with a different identity Try opening Copilot Chat in a new VS Code profile If none of the above resolves it, this is likely a backend entitlement sync issue, and GitHub Support will need to reattach Copilot Chat quota to your account. |
Beta Was this translation helpful? Give feedback.
-
|
I have an active GitHub Copilot Pro+ subscription on my account (username: Selin611). Proofs from my side: GitHub Billing → Copilot Pro+ is active GitHub Settings → Copilot features are enabled VS Code Copilot extension is authenticated and working for code completion Copilot backend logs confirm valid token and successful requests (gpt-4.1-copilot) However, Copilot Chat is consistently failing with the following error: 402 quota_exceeded This happens across: multiple VS Code sessions restarts re-logins extension reloads So this does not appear to be a local or client-side issue. Based on the behavior and the error SKU, it looks like Copilot Chat is still treating my account as “free_limited_copilot”, even though Copilot Pro+ is active on the billing side. This strongly suggests a server-side quota / entitlement mismatch, where the Copilot Chat quota is not correctly attached to my Pro+ subscription. Other users are reporting the same pattern: Pro active in billing Copilot Chat returning free_limited_copilot Issue resolved only after GitHub backend intervention Request: I’m happy to provide: screenshots of billing and Copilot settings VS Code Copilot logs timestamps of failing requests Thank you in advance — this appears to be a backend synchronization issue rather than a user configuration problem. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Copilot Feature Area
Copilot in GitHub
Body
Hello.
My GitHub account has an active Copilot Pro subscription.
However, Copilot Chat returns:
402 quota_exceeded
sku: free_limited_copilot
This happens across multiple VS Code sessions.
Billing page shows Copilot Pro active.
Could you please check whether my Copilot Chat quota is correctly attached to my account?
Beta Was this translation helpful? Give feedback.
All reactions