GitHub Copilot: AI Credit Usage Visibility Per Billing Cycle
GitHub CopilotGitHub Copilot Business and Copilot Enterprise users can now see their actual AI credit consumption for the current billing cycle directly on the Copilot usage page in account settings. Previously the page only showed usage as a percentage of an allocated budget, which left users without an individual budget unable to see how many credits they had actually used. The updated page now shows total credits consumed for users without a budget, and credits used against the total budgeted amount for users who have one.
Featured Video
A video we selected to help illustrate this changelog
Key Takeaways
- Percentage-only reporting is gone for users without a configured budget, who previously had no way to see their actual credit consumption.
- Two display modes now exist: total credits used for unbudgeted accounts, and credits-used-against-budget for accounts with a defined limit.
- Community frustration drove the change, with GitHub Community threads describing usage-based billing as confusing and, for some teams, financially painful without better visibility.
- Third-party tooling emerged to fill the gap, including community dashboards and VS Code spend meters built specifically to surface AI credit consumption before GitHub's own UI caught up.
- The change is scoped to Business and Enterprise plans, the tiers most exposed to budget-driven throttling and overage risk.
- It complements, not replaces, admin-level controls, since organization-wide budgets, cost center pools, and overage policies are still configured separately by administrators.
Sources & Mentions
5 external resources covering this update
GitHub Copilot AI Usage Dashboard | Monitor AI Credits Like a Pro
YouTube
How to Track GitHub Copilot Pro Premium Requests | Explained: 1x vs 0.33x LLM Costs & Snooze stop
YouTube
VS Code 1.125 Adds Copilot Spend Meter After Billing Shock
Visual Studio Magazine
All GitHub Copilot plans are now on usage-based billing (FAQ)
GitHub Community
GitHub Copilot AI Credits Are Unfair, Expensive, and Killing Real Development Workflows
GitHub Community
A Clearer View of AI Credit Spend
GitHub has updated the Copilot usage page in account settings so that Copilot Business and Copilot Enterprise subscribers can finally see how many AI credits they have consumed within the current billing cycle. The change addresses a gap that emerged after GitHub moved Copilot to usage-based billing, where every chat message, agent task, and code review interaction draws down a shared pool of credits.
The Problem With Percentage-Only Reporting
Before this update, the usage page displayed consumption purely as a percentage of an allocated budget. For subscribers whose administrators had not configured an individual budget, that number was meaningless; there was nothing to be a percentage of. As a result, many users had no reliable way to understand how much of their monthly allowance they had actually burned through, particularly during the early rollout of usage-based billing when consumption patterns were unfamiliar and, for some teams, surprisingly steep.
What Changed
The usage page now adapts based on whether a budget exists for the account:
- Without a budget: GitHub Copilot now shows the raw total of AI credits used during the current cycle.
- With a budget: GitHub Copilot shows credits used out of the total budgeted amount, preserving the percentage context that budget-constrained users still find useful.
This dual display means every subscriber, regardless of how their organization has configured billing, gets a concrete, actionable number instead of an ambiguous or missing metric.
Why It Matters
Usage-based billing ties feature access directly to credit consumption, so visibility into real-time spend has quickly become one of the most requested improvements from the developer community. Being able to see actual credits used, rather than an opaque percentage, helps individual developers pace their usage across a billing cycle, understand which activities (chat, agent tasks, code review) are consuming the most credits, and avoid unexpected throttling or overage charges near the end of the month. GitHub points users to its documentation on usage-based billing budgets for further detail on how credit pools and resets work.