Copilot's New Usage-Based Billing System - Improvement #194191
Replies: 2 comments
-
|
💬 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.
-
|
Hi @Breslov We have an official discussion post dedicated to GitHub's move to usage-based billing where you can find detailed information, updates, and join the conversation: GitHub Copilot is moving to usage-based billing. Please head over to that thread for the latest details and to share your feedback or questions. We'll be closing this discussion to keep things organized. Thank you for understanding! 🙏 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Account Related
Body
I am writing to provide feedback on the upcoming transition to usage-based billing for GitHub Copilot.
While I understand the need to align pricing with the compute demands of an agentic platform, I believe the current structure could more accurately reflect a "pay-per-use" philosophy.
I propose the following enhancements to the GitHub AI Credits system, to achieve a truly, symmetric "usage-based system":
Credit Rollover: Monthly AI Credits should not expire. To ensure customers only pay for what they consume, unused credits should automatically roll over and accumulate.
Subscription Suspension/Resumption: To avoid unnecessary billing, the system should allow users to set credit thresholds. If accumulated credits exceed a user-defined limit, monthly billing should pause and only resume once the balance drops below a secondary threshold.
Implementing these features would create a more transparent and equitable system that respects the customer's financial commitment.
Thank you for considering this feedback.
Beta Was this translation helpful? Give feedback.
All reactions