Copilot billing needs per-project usage attribution and enforceable project budgeting

[fliglesmork]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot in GitHub

Body

am requesting escalation of a GitHub Copilot billing and usage-reporting limitation to both the Copilot billing team and the Copilot product team.

I develop multiple applications with GitHub Copilot. My additional Copilot usage is currently presented as an aggregate account-level amount. There is no reliable report showing how much additional usage or cost was incurred by each application, repository, solution, workspace, or chat session.

This creates a material accounting problem. I have already incurred approximately $300 in additional usage, may work on approximately seven applications, and may authorize a much larger total budget—potentially as much as $10,000. An account-wide total does not tell me which application generated each portion of that expense. I need project-level attribution to charge development costs to the correct application and maintain separate project budgets.

Manual before-and-after snapshots are not an adequate solution because billing data can be delayed, work can overlap, and developers can switch between applications. Allocation based only on time is also inaccurate because different models and requests can have different billable usage.

Please add or escalate a request for the following capabilities:

Attribute each billable Copilot request to the active repository, solution, workspace, and chat session at the time the charge occurs.
Allow repositories and workspaces to be grouped under a user-defined application or project billing identifier.
Show monthly and lifetime premium-request usage and estimated or final cost by application.
Allow a separate warning threshold and enforceable spending limit for each application.
Provide CSV and API exports suitable for client, application, and internal cost-center chargeback.
Record requests made outside a project under an explicit “Unassigned usage” category.
Permit privacy-preserving project identifiers so reports do not need to expose private repository or client names.
Show reporting latency and distinguish pending usage from finalized charges.
Please answer the following questions:

• Does GitHub currently retain any repository, workspace, solution, or chat identifier with each billable Copilot request?
• Is any existing report or API capable of returning Copilot additional usage by project?
• Can separate project-level budgets or hard limits be configured today?
• If not, can this ticket be attached to an existing feature request and can you provide its tracking reference?
• What supported method does GitHub recommend for auditable per-application chargeback?
• Can a billing or Copilot product specialist respond, or can a callback be arranged if that option is available for my plan?

This is not merely a request for a different display of the same account total. The required capability is transaction-time attribution of billable usage to a project, followed by project-level reporting and budget enforcement. Without that association, an accurate allocation cannot be reconstructed afterward.

I picked Copilot Pro but really I have Copilot Max, my account name is @fliglesmork

i have started a standard support ticket , but was hoping others would chime in on this

Thank you.
Edward Battaglia

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

[ItsAnjaliSharma]

I strongly agree with this request. Project-level attribution for Copilot usage would be especially valuable for developers and teams managing multiple applications or client projects.

An account-level usage total makes it difficult to:

• Track the actual Copilot cost of each project
• Charge costs accurately to different clients or applications
• Set independent budgets for separate projects
• Identify which project is generating unexpected premium usage

A repository/project-level usage identifier attached to each billable request would make this much easier. Ideally, GitHub could also provide API/CSV reporting with usage, estimated/final cost, project identifier, and reporting status.

Per-project spending limits would be even more useful, particularly for teams managing multiple applications with different budgets.

I hope GitHub considers this as a billing and cost-management feature rather than only a reporting/UI improvement. This would make Copilot much easier to use for professional development and client-based projects.