New Copilot usage limits are too restrictive for paid Pro+ workflows, and the reset date message appears incorrect

[ADP-CH]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Body

Hi GitHub team,

I would like to share feedback about the new Copilot usage limits that started on June 1.

I have a GitHub Copilot Pro+ account and, depending on the month, I also spend around €200–€300 on additional usage. Until now, this was usually enough for my normal workflow across roughly five working days per week.

Since the new limit model started, the experience has become very frustrating. I reached my limits much faster than expected, even though I am already on a paid plan and paying extra for additional usage. For professional users who rely on Copilot Agents for real project work, the current limits feel too restrictive and make it hard to plan work reliably.

There also seems to be a bug or at least a confusing message in the limit reset information. The UI says:

“You’ve reached your weekly rate limit. Please wait for your limit to reset on May 25, 2026 at 12:00 AM…”

However, today is June 3, 2026. So the reset date shown is already in the past. That makes the message impossible to act on. I cannot know whether I should wait, switch models, buy more usage, or whether something is wrong with my account.

What I expected:

1. Copilot should show a correct and future reset date.
2. The paid Pro+ plan plus additional paid usage should provide enough capacity for serious professional workflows.
3. The UI should clearly explain which limit was reached, when it resets, and what the user can do next.

What happened instead:

My work stopped because of a weekly rate limit.

The reset date shown is in the past.

I am also shown that I have used 90% of my monthly usage limit, which creates additional confusion about whether this is a weekly, monthly, premium request, or model specific limit.

For users who use Copilot Agents in real projects, this is a major workflow blocker. I understand that limits are necessary, but the current experience feels unclear, too restrictive for paid heavy users, and currently also affected by an incorrect reset date message.

Screenshots are attached.

Thank you.

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