Message to Copilot Team: Usage, Trust, and Empathy

[aridjemana]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot in GitHub

Body

Dear Copilot Team,

• Token model is fair: I accept the need for usage‑based billing to secure infrastructure costs.
• Calculation feels broken: Simple CMS front‑end tasks consumed thousands of tokens, while other AI tools handled larger workloads with far fewer cycles. This makes Copilot unpredictable and unsustainable, even for Pro Plus users.
• Trust matters: Trust is fragile — once shaken, it lingers. Developers feel betrayed not because of cost control, but because of how the change was implemented and communicated.
• Forgiveness is possible: Giants can make mistakes, but if they face issues openly and rebuild with humility, the community can forgive.

And to the engineers behind Copilot: I know how it feels to make a change in production and then see unexpected consequences. Mistakes happen, and often leadership decisions amplify the pressure. Please know many of us don’t see this as one person’s fault. We respect the work you’ve done and hope you’re treated fairly inside the company. because the work you’ve done has already helped countless developers.

My hope: Review how token usage is calculated, and consider mechanisms that make Copilot sustainable for heavy users without cutting them off mid‑month. Nobody is perfect, and nobody stays angry forever — but trust requires care to restore.

Respectfully,
Ari

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