Copilot Pro+ Blocking Premium Models Immediately After Subscription!!! Usage Limit Bug

[sumioshi]

Select Topic Area

Bug

Copilot Feature Area

General

Body

Hi GitHub Team,

I just subscribed to GitHub Copilot Pro+ (US$ 39/month) and I'm already facing a major issue.

After only a couple of interactions with Claude Sonnet 4, I received the warning:

"You have exceeded your premium request allowance. We have automatically switched you to GPT-4.1..."

This makes no sense, considering:

• My subscription is brand new.
• I’ve barely used any premium models.
• My billing page shows $0 usage.
• I haven’t enabled any additional paid premium requests.
• All premium models (Claude Sonnet 4, Claude Opus, etc.) are now blocked.

It feels like my account didn't properly reset or initialize the premium quota (1,500 requests/month). I've checked all settings, removed budgets, reviewed every possible cause still blocked.

I also found this discussion with the exact same issue:
https://github.com/orgs/community/discussions/161563

Please escalate this bug. We're paying for premium features that are currently unusable.

Thanks in advance.

[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. ⭐

[BrunoJuchli]

After I was subscribed to GitHub Copilot Enterprise by org admin I cannot use the premium requests at all, receiving errors like:

(copilot-swe-agent)

I could not start work on this issue because you've used up the premium requests allowance included in your Copilot subscription this month, and your subscription does not allow additional paid usage. To try again, just unassign and reassign this issue to me.

or

Your session could not start because you've used up the premium requests allowance included in your Copilot subscription this month, and your subscription does not allow additional paid usage. To retry, just leave a comment on this pull request asking me to try again.

The org admin can do the same actions successfuly

[admaiorastudio]

same issues here. Bought the subscription yesterday and it's already broken. Not a good start for 40$/month

[BrunoJuchli]

Close to a day later, it has now magically resolved for me. Eventual consistency? ;-)

[mohammad-malik]

they should just cancel this change and revert to having Pro and Enterprise. A new tier is unnecessary and just plain overpriced for how little you get for 40$

[dogia]

[Akash1134]

Hi everyone,

We shared your reports with the appropriate team earlier and this issue should now be resolved.

Could you please confirm the current experience and share feedback.

Thanks!