GitHub Copilot's New Billing Model: Unacceptable Overpricing Making the Tool Unusable

[biroMann]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot Agent Mode

Body

I'm reaching out as a frustrated Pro+ user regarding the recent changes to GitHub Copilot's billing model. After just one simple code modification, I saw 10% credits consumed, at this rate, it's becoming nearly impossible to use this tool effectively.

This new pricing structure feels disconnected from the real needs of developers.
The AI-generated code often leads to bugs that require additional requests, further driving up costs. It's disheartening to think that this approach could alienate so many users. I genuinely hope GitHub will reconsider this model and strive for a more user-friendly solution. Thank you for listening.

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

[dbestechno]

3 Days In. Already Past 60%.
Three days. Not a sprint, not a hackathon, not a stress-test. Just regular, everyday use — and the meter is already past the halfway mark, racing toward empty like it was designed to run out.
Whoever built this new billing plan clearly tested it in a vacuum. The limits feel arbitrary. The usage tracking is opaque. And the upgrade nudges? Already showing up on day two.
This isn't a pricing model. It's a pressure campaign.
A plan that can't survive a Tuesday is not a plan. It's a trap.
Normal use should not feel like rationing. If you're anxious about every action you take within a product you're already paying for, the product has failed you. Full stop.
Three days in, over 60% consumed, twenty-seven days still to go. Someone designed this. Someone approved this. And someone needs to fix it.

[biroMann]

I moved to Claude.ai, can run in vscode/codium
much much better, if i knew it before, i would have moved before

Hello,

We have provided more details and a FAQ about usage-based billing in this discussion, which may be updated if new information becomes available.

To keep conversations all in one place and to ensure you receive timely updates, we’ll be closing and locking this post and recommend you comment on or subscribe to the discussion linked above. Thank you!