GitHub Copilot usage-based billing — significant budget overage in first two weeks #198911
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.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Copilot in GitHub
Body
I've been testing the new usage-based billing model and wanted to flag a concern: on day 13 of my subscription, I've already exhausted 100% of my base budget plus $15 in overages.
For context — during the equivalent period last month under the old flat-rate model, I used only ~50–60% of my base allowance, despite working at similar intensity and with less conservative habits than I'm using now.
The issue: The new model appears significantly more expensive for my actual workflow, and much less predictable. This makes it harder to budget for a development tool I rely on daily.
I'm now seriously considering alternatives (Cursor Pro, other environments) where costs are more straightforward.
Question: Is this typical user feedback you're seeing? Are there any plans for better usage transparency, tier adjustments, or improved budget controls to help users like me manage costs predictably?
Beta Was this translation helpful? Give feedback.
All reactions