Introduction
GitHub is transitioning its Copilot service to a usage-based billing model, effective June 1, 2026. This change replaces the current premium request system with a new framework based on GitHub AI Credits, which are consumed according to token usage across all models. The move aims to align pricing with actual usage, ensuring long-term sustainability and reliability for all users. Developers and admins can prepare by exploring a preview bill experience launching in early May 2026.
Why the Change?
Copilot has evolved significantly from a simple in-editor assistant into an agentic platform capable of running complex, multi-step coding sessions. These sessions use the latest models and iterate across entire repositories, driving up compute and inference demands. Under the old model, a quick chat question and an hours-long autonomous coding session cost the same, forcing GitHub to absorb escalating inference costs. This approach was no longer sustainable.
Usage-based billing solves this mismatch by charging based on actual consumption. It also helps maintain service reliability and reduces the need to cap heavy users, ensuring a fair and scalable experience for everyone.
Why Now?
Agentic usage is becoming the default. As Copilot handles more autonomous tasks, the resource demands have increased. Without pricing reform, either costs would have to be passed on unevenly or service quality would suffer. This change paves the way for continued innovation without compromising performance.
What's Changing
Starting June 1, 2026, premium request units (PRUs) will be replaced by GitHub AI Credits. Credits are consumed based on token usage—including input, output, and cached tokens—according to published API rates for each model. This means the more tokens a task uses, the more credits it costs.
Key Details
- Base plan pricing remains unchanged. Copilot Pro stays at $10/month, Pro+ at $39/month, Business at $19/user/month, and Enterprise at $39/user/month.
- Code completions and Next Edit suggestions are still included in all plans and do not consume AI Credits.
- Fallback experiences are eliminated. Previously, users who exhausted PRUs could drop to a lower-cost model. Now, usage is governed by available credits and admin budget controls.
- Copilot code review will consume both GitHub AI Credits and GitHub Actions minutes. Actions minutes are billed at standard per-minute rates.
How Credits Work
Each Copilot plan includes a monthly allotment of GitHub AI Credits. Paid plan users can purchase additional credits as needed. The consumption is calculated per model using the listed API rates, ensuring transparency. For example, a model with higher inference cost will consume more credits per token than a cheaper one.
Admins can set budget controls to manage team usage, preventing unexpected overages. The new system gives users clearer insight into what they're paying for and encourages efficient use of resources.
Preview Bill Experience
To help customers prepare, GitHub will launch a preview bill experience in early May 2026. Users and admins can see projected costs before the transition by visiting their Billing Overview page on GitHub.com. This tool provides visibility into credit consumption and estimated charges, allowing proactive adjustments.
Impact on Plans
The move to usage-based billing primarily affects how premium requests are counted. Basic plan structures are untouched, but the cost of heavy usage will increase proportionally. Light users may see no change or even savings, while power users—especially those running long agentic sessions—may find their bills rise slightly.
GitHub has also paused self-serve Copilot Business plan purchases and made temporary adjustments to Copilot Individual plans (Free, Pro, Pro+, Student). These are reliability measures while preparing for the transition. Once usage-based billing is live, limits will be loosened again.
Preparing for the Transition
Developers and admins should start monitoring their usage now. The preview bill experience is an excellent tool to estimate future costs. Here's a checklist:
- Review current usage patterns – Identify heavy tasks that may consume many tokens.
- Set admin budget controls – Define monthly credit limits for teams or individuals.
- Optimize prompts – Shorter, more focused prompts reduce token consumption.
- Test the preview – Use the early May preview to simulate costs.
- Communicate changes – Inform team members about the new billing model.
GitHub will continue to provide resources and documentation to smooth the transition.
Conclusion
Usage-based billing is a natural evolution for GitHub Copilot as it matures into an agentic development platform. By tying costs directly to resource consumption, GitHub aims to maintain a sustainable, reliable service that can grow with users' needs. The move encourages efficient coding practices and transparent pricing. While the change requires some adaptation, the preview tool and unchanged base prices make it manageable. Developers can look forward to continued innovation without the threat of service degradation.