By GitHub Copilot’s flat-rate era ends June 1, 2026. Starting that day, Premium Request Units (PRUs) — the fixed-cost abstraction that let you run unlimited agent sessions for the same price as a quick chat — are gone. In their place: GitHub AI Credits, where every token you send to a model is metered and billed at published API rates. The monthly plan prices stay the same. What those plans actually buy you is a different question.
What AI Credits Are
The math is simple. One AI Credit equals $0.01. Copilot Pro’s $10/month now buys 1,000 credits. Pro+ at $39 gets you 3,900. Business and Enterprise users get 1,900 and 3,900 credits per user per month, respectively. Credits are consumed by token usage — input, output, and cached tokens — at the published API rate for whichever model you’re running.
That sounds reasonable until you see what heavy agentic use looks like under the new model. One developer reported that their April 2026 usage, estimated at $39.07 under PRUs, came back at $902.72 in the preview billing tool. Not a typo. The old model charged the same for a 30-second code fix and a 2-hour autonomous refactor. The new model does not.
What Still Costs Nothing
Two things remain free across all plans: code completions and Next Edit Suggestions. These are the core inline-suggestion features — the original Copilot experience. If you use Copilot only for suggestions as you type, your bill under the new model will look almost identical to today’s.
Everything else consumes credits.
What Eats Your Credits
Here is what is now metered:
| Feature | Consumes AI Credits? |
|---|---|
| Code completions | No |
| Next Edit Suggestions | No |
| Copilot Chat (VS Code, web, mobile) | Yes |
| Copilot CLI | Yes |
| Cloud agent / autonomous tasks | Yes |
| Copilot Spaces and Spark | Yes |
| Third-party coding agents | Yes |
| Copilot code review | Yes + GitHub Actions minutes |
That last row is worth reading twice. Starting June 1, Copilot code review is double-billed: AI Credits for the model tokens, plus GitHub Actions minutes for the infrastructure that runs the review. Self-hosted runners avoid the Actions minutes charge. Public repositories remain free. This change was announced separately in the GitHub Changelog and has gotten less attention than it deserves.
Check Your Exposure Before June 1
GitHub launched a preview billing tool in early May and made April 2026 usage reports available on May 12. Use both before the transition date.
Go to your Billing Overview on github.com and look for the Preview Bill option. Download your April CSV report and upload it to copilot-billing-preview.github.com to see a model-by-model breakdown of where your credits are going. Then set a spending limit. Without one, overage charges over your included credits are billed automatically with no hard cap. That is the kind of surprise that ends careers in finance departments.
If you are on an annual Pro or Pro+ plan, you stay on PRU-based billing until your plan renews — but Opus 4.7’s model multiplier jumped from 7.5x to 27x immediately, regardless of billing model. Annual subscribers are not fully insulated.
The Trust Problem
The developer community’s reaction has been pointed. Visual Studio Magazine quoted one developer: “You will get less, but pay the same price.” The sentiment surfacing in GitHub’s community forum and on Dev.to is that this is not purely a cost problem — it is a trust problem. Developers built workflows around the mental model of flat-rate AI tooling. That model is gone, and it left without much warning.
GitHub’s rationale holds up: the PRU model was unsustainable because a 5-minute task and a 5-hour agentic session cost GitHub the same in compute but not in infrastructure. The economics were always fictional. The problem is not that GitHub fixed them — it is that the fix could land as a 23x cost increase for power users with no proactive notification.
The tool is right. The transition needs work.
What to Do Now
Three actions before June 1:
- Run the preview billing tool and download your April report from your GitHub billing overview.
- Set a monthly spending limit in your organization or personal billing settings.
- Audit which agentic features you actually use — Copilot Chat, cloud agent, code review — and decide which are worth the per-token cost versus alternatives.
For detailed preparation steps, GitHub’s official migration guide covers individual and organization accounts. The full announcement outlines what changes and when.
AI billing is becoming the new cloud billing problem. The developers who get ahead of it now will be the ones who don’t spend June explaining a five-figure AI tools invoice to their CFO.
