Show GitHub Copilot Real and applicable Rate Limits on Dashboard #161280
Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Copilot Feature Area
Copilot Workspace
Body
🚀 Feature Request: Show GitHub Copilot Rate Limits on Dashboard
Summary
GitHub Copilot appears to have hidden rate limits that throttle completions during heavy usage. Please expose these limits transparently on the GitHub.com dashboard or via API.
🎯 What I’m Asking For
I want a clear, visible rate limit status for GitHub Copilot, similar to what exists for the GitHub REST API (
/rate_limit), including:limit: total completions allowed per time windowremaining: how many completions are leftreset: timestamp or countdown until limit resetsThis should be available:
https://github.com/settings/copilotor/account/usage)🔍 Why This Matters
Right now, Copilot usage feels like a black box. If completions suddenly stop or slow down, there’s no feedback as to why — and no visibility into when it’ll be available again.
As a paying user, this creates friction and anxiety similar to “energy systems” in mobile games. I need a visible “fuel gauge” so I can:
✅ Benefits
💬 Final Thoughts
If rate limiting is part of Copilot’s design (which it clearly is), then users deserve transparency. Show us the limits — we’ll respect them. Just don’t make us guess.
Thanks,
perikiyoxd
Copilot Subscriber & Developer
Beta Was this translation helpful? Give feedback.
All reactions