Copilot-Pro not initiating

[DarkMatter-DMOS]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Other

Body

Upgrading from Copilot Free to Copilot Pro does not activate throughout the platform, I have two accounts the second I had to create as I have not been getting any form of response from GitHub Support on the matter, upgrading to Pro from Free does not reflect correctly in the account, yes there are timeframes for the activation and population within the profile this does not take weeks to initiate. VSCODE Copilot dies not see this even though a new account is immediately upgraded during registration and subscribed to Copilot Pro, any utilisation of Copilot results in shutdown due to it still being seen as free and not pro. Support is non existent in this regard, no matter how often you try and contact support its a dead.

I am having to resort to following the legal route as there is absolutely no response from Github.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[DarkMatter-DMOS]

I don't think I will get any form of response from GitHub on this matter, hence why I am having to follow the legal route to get this resolved or to take it further.

[mehediScriptDev]

did you checked your bank statement to confirm payment actually done or not?

and what about github web dashboard, is it showing pro or still free?

[DarkMatter-DMOS]

Bank confirmation there GitHub confirmation there. One section on GitHub shows pro the other section shows free.

[syedahmedx3]

💡 The Fix: Force an IDE Token Purge

This behaviour usually happens because VS Code aggressively caches your GitHub authentication scopes. Even if your billing dashboard says "Pro," your editor is still passing the old "Free" tier OAuth token back to the Copilot API, causing an immediate shutdown.

Furthermore, immediately upgrading a secondary account right after registration often triggers GitHub's automated anti-fraud flags, throttling the API. Stick to your primary account and run this reset:

1. Nuke the Cached Token

• In VS Code, click the Accounts icon (bottom left) and Sign Out of your GitHub account.
• Close VS Code entirely.
• Open your terminal and run this to clear your local Git credential manager cache:

  git credential-manager reject [https://github.com](https://github.com)

2. Refresh the Session

• Reopen VS Code.
• Sign back into your primary account when prompted by the Copilot extension.
• This forces GitHub to issue a brand new OAuth token containing your upgraded Pro permissions.

3. Verify Model Scopes

• Go to your GitHub profile Settings > Copilot and ensure your access permissions and models (like Claude or GPT-4o) are checked as active.

[DarkMatter-DMOS]

Thank you for your recommendation. I tried that, and it still references Free and does not reference the Pro not sure why I signed up for Pro before I linked VSCODE.

[v-coder247]

Hi @DarkMatter-DMOS, thanks for being a part of the GitHub Community!

The Projects & Issues category is meant for discussions related to GitHub features areas that don’t have their own explicit category. I will be moving your post to Copilot Conversations, as it may be more relevant there and might help someone give you a nudge in the right direction 😄

Hi @DarkMatter-DMOS,

Did you attempt to upgrade your Copilot subscription after April 20th? If so, we've recently announced the following changes to GitHub Copilot’s Individual plans to protect the experience for existing customers: pausing new sign-ups, tightening usage limits, and adjusting model availability. Please visit the GitHub Blog: Changes to GitHub Copilot Individual Plans for more details.

If you’ve purchased Copilot through Apple or Google Play, please reach out to them directly for a refund.

I also see that you have a GitHub Pro account, are those the charges you're mentioning? The plan names are similar but GitHub Pro does not include access to Copilot, and new signups for Copilot Pro/Pro+ are currently paused.

Lastly, if none of the information above is applicable, the only place to go for answers to account-specific questions like this one is opening a ticket on our Support page.

This is a public forum, and the community is unable to assist with nor escalate your ticket, but we can assure you it is in the right place. There are an extremely high volume of Support tickets right now, yours will be answered in the order it was received based on the amount of tickets ahead of yours. Please open only one ticket per request.

As no other Community Discussions team members will be able to provide additional help with account related questions I am going to close this discussion. We appreciate your understanding and patience while Support works through your request!