Unreliable service - if you wanted to use it for professional work, it is not for you

[annsk]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot Agent Mode

Body

The "Pro+" Illusion
I am posting this here because the gap between GitHub Copilot’s marketing and the actual developer experience has become unacceptable for professional use. I have specifically configured a high budget on my Pro Plus subscription to ensure my workflow remains uninterrupted, yet the service is currently acting like a throttled trial account.

The Refactoring Wall
Professional engineering is not just about generating boilerplate snippets; it involves deep refactoring across dozens of files and debugging complex E2E test suites. This is exactly where a "Pro" tool should shine, but instead, it is where Copilot fails.

After just a few substantial requests during a refactor (editing ~30 files), I am hitting aggressive rate limits. Even worse, the service often fails to provide a clear error—it simply hangs indefinitely. I am losing more time waiting for the "premium" service to respond than it would take to do the work manually. This isn't just a minor inconvenience; it is a workflow killer.

Operating in a Black Box
What is the point of a "Pro+" tier if we are forced to work with zero transparency? We are paying for a professional-grade service, yet we are given no tools to manage it. There is no documentation on what the actual limits are for users, especially high-paying, making it impossible to plan a workweek or estimate task completion.

My Questions for the GitHub Team
If GitHub wants Copilot to be the industry standard for senior developers and engineering leads, it needs to be predictable.

1. How are we supposed to rely on this for architecture-heavy tasks if we are throttled without warning?
2. When will you provide a real-time usage meter so we can actually manage the budget we are paying for?

Right now, this feels like a hobbyist toy rather than a professional IDE integration. I would love to hear if other Pro+ users are being ground to a halt the moment they try to do something more complex than writing a single function.

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

[pepperymilkcap]

This has been happening few days now and has gotten so bad that The Register has written an article on it.

https://www.theregister.com/2026/04/15/github_copilot_rate_limiting_bug

More people with the same problem:
https://github.com/orgs/community/discussions/192707
https://github.com/orgs/community/discussions/192435
https://github.com/orgs/community/discussions/192723
https://github.com/orgs/community/discussions/180092

I highly recommended updating us on the status of your rate limit (whether it has been fixed or not) every couple of hours to make sure this problem is visible enough to the people who need to see it.