GitHub Copilot April Usage Reports Ready for June Billing Shift
GitHub released April usage reports showing how Copilot activity converts to AI credits before the June 1 billing switch. Download yours to forecast costs and identify top consumers—but watch for data gaps.
TL;DR
- GitHub released April usage reports showing how Copilot activity converts to AI credits before June 1 billing launch
- Admins and individual users can download reports to forecast costs and identify top consumers
- Reports have known gaps: missing 0x model data, duplicate entries, and incomplete code review estimations—treat as directional, not final
What Dropped
GitHub is letting Copilot Business, Enterprise, Pro, and Pro+ users download April activity reports that estimate AI credit consumption. This is a preview tool ahead of the June 1 switch to usage-based billing. Admins can access enterprise-wide data; individual users get personal usage breakdowns.
The Dev Angle
The report shows which models and surfaces (IDE, CLI, web) drove the most consumption, and identifies your team's top Copilot users. You can use this to estimate monthly AI credit spend before the new billing model kicks in and adjust team allocations or budgets accordingly.
GitHub is transparent about the report's limitations. April 1–24 data for 0x models is missing (roughly 2% of activity at scale). Duplicate entries may appear for April 24–30 due to a data backfill issue. Some code review entries lack AI credit estimations because they were charged directly to organizations or came from unlicensed users—these show 0 credits due to a data gap.
The takeaway: use this as a directional signal for cost shape and consumption patterns, not as a recalculated invoice. Monitor May data as well to refine your estimates before June 1.
Should You Care?
If you run a Copilot Business or Enterprise deployment, yes—download the report now to understand your team's usage footprint and plan budget adjustments. If you're on Copilot Pro or Pro+, grab your personal report to see if your usage patterns will shift your costs under the new model.
If your team relies heavily on 0x models, the April 1–24 gap means you should weight April 24+ data more heavily in your forecasts. If code review is a major part of your workflow, expect the estimations to improve once GitHub fixes the data issue.
The Copilot pricing overhaul introduced flex credits and new plan tiers, so this report is your first real look at what that consumption actually costs your team. Download it, share it with finance, and plan accordingly.
Source: GitHub Changelog