Copilot token billing should be based on session start time, not server processing completion time.

[yamahaNK]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

Hello,

I would like to raise a serious concern regarding the billing logic under the new usage-based billing system (AI Credits).

Currently, GitHub calculates Copilot token consumption based on the time the server finishes processing the request, rather than when the user initiated it. This causes a critical issue for users deactivated at the end of the month.

For example, a user who was deactivated on May 31st initiated a request before their access was removed. However, because the server finished processing that request after midnight, the tokens were incorrectly charged against our June organization pool.

This logic is completely unfair and flawed. A deactivated user should not be able to consume the next month’s tokens under any circumstances.

GitHub Copilot billing must be based on the user-initiated session start time (timestamp), not the server's delayed processing completion time.

I hope the GitHub product team takes this feedback seriously and fixes this calculation logic to prevent unexpected billing shocks for organization administrators.

Thank you.

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