I am a GitHub Copilot Pro user and I want to share feedback about Copilot Pro AI Credits usage has become unpredictable and too costly after token-based billing

[ketankotak13]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot Agent Mode

Body

I am a GitHub Copilot Pro user and I want to share feedback about the new AI Credits usage model.

My Copilot usage suddenly reached around 73% very early in the monthly cycle. This is surprising because my normal development workflow has not changed significantly. The new token-based usage model feels much less predictable compared to the earlier request-based model.

For regular developers, it is very difficult to understand how much usage will be consumed before running Copilot Chat, Agent mode, premium models, or large-context prompts. A single broad coding task can consume credits very quickly, especially when repository context, agent loops, and generated code are involved.

I have now configured a $0 budget with “Stop usage” enabled, but that only prevents extra billing. It does not solve the main problem: Copilot Pro can become unusable very early in the month without enough warning or control.

My requests:

1. Show estimated AI Credit usage before running Agent mode, premium models, or large repository-context tasks.
2. Provide a clear breakdown of which feature/model consumed the credits.
3. Allow Copilot Pro users to disable premium models and Agent mode from consuming credits unless manually approved.
4. Add stronger warnings when a prompt or task may consume high credits.
5. Consider increasing included AI Credits for Copilot Pro or providing a more predictable usage model for individual developers.

The current model feels significantly more expensive and unpredictable for normal software development work.

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

[phakphompleng1122-design]

@ketankotak13