GitHub Copilot moves to usage-based pricing June 1—what changes

usage-based pricing – GitHub Copilot is switching to AI Credits tied to token usage on June 1, 2026. Base subscription prices stay put—but running out of credits means you can’t use the service.
GitHub is changing how people pay for Copilot, and the date is close: June 1, 2026.
The shift to usage-based billing is the big headline. but the deeper story is how Copilot has evolved—and how that evolution is colliding with real compute costs.. The change will start with all GitHub Copilot plans. where customers will be billed through monthly “AI Credits” based on token consumption (including input. output. and cached tokens).
Why token-based billing is landing now
The current Copilot pricing framework uses a system called Premium Request Units (PRUs).. Under the new approach. GitHub says the service is no longer the same kind of programming assistant people originally subscribed to.. Copilot is being positioned as “agentic. ” meaning it can handle longer. multi-step coding sessions across repositories rather than simply producing quick code suggestions.
That matters because longer sessions typically mean more work for the underlying models: more inference. more iterative steps. and more data moving through the system.. GitHub’s argument is straightforward: the PRU model didn’t scale sustainably when a brief chat can be followed by a lengthy autonomous coding run at a similar cost.
For readers, the practical impact is this: you may still pay the same base subscription price, but your ability to use the higher-intensity features will be governed by how many tokens your workflows consume.
What Copilot users will notice on June 1
GitHub says the monthly subscription prices for now remain unchanged. Copilot Pro will stay at $10 per month, and Copilot Pro+ stays at $39 per month. But those monthly fees will now come with matching AI Credits—$10 in credits for Pro, and $39 in credits for Pro+.
Code completions and Next Edit suggestions will continue to be included without consuming AI Credits.. That distinction is important: many developers may feel little day-to-day change if their usage is mostly about short, interactive assistance.. The billing pressure shows up when people rely on Copilot for extended, agent-like runs.
There’s also a hard edge to the transition.. With PRUs, users could previously “downshift” to less capable options when capacity was reached.. GitHub indicates that under the AI Credits model. running out of credits will effectively stop access—meaning additional usage will require buying more credits.
Plans, pooling, and admin controls
Not every plan changes immediately in the same way. GitHub says annual plans will continue on the PRU system until they expire, then move onto the newer model. There are also options for customers to convert early to monthly plans with prorated credits.
Copilot Business and Copilot Enterprise retain their existing per-seat pricing, but will similarly include AI Credits with each seat.. GitHub also plans to introduce pooled usage across teams. which can reduce the “stranded capacity” problem where one developer burns through credits while another finishes the month with unused allotments.
For larger organizations, administrators will gain budget controls at levels that map to how companies actually manage software spend—cost centers, users, and enterprise-wide limits. They’ll also be able to cap or allow additional purchases when pools are exhausted.
The credits preview—and why it’s a big deal
To help customers prepare, GitHub plans to launch a preview of projected bills in early May.. That timing is not just a courtesy—it’s a response to the anxiety that always comes with usage-based pricing.. If you only learn your likely overage once the new billing cycle starts, the cost shock tends to be worse.
With token-based systems, costs can behave differently than people expect.. Token usage isn’t just about length of prompts; it’s influenced by what the agent does next. how much it iterates. and how cached context is handled.. In other words, two developers doing “the same job” in different ways can see very different token consumption profiles.
GitHub also announced promotional credits for the transition window—covering June, July, and August 2026.. Business customers will receive additional monthly credits, and Enterprise customers will receive a larger promotional allocation.. Still, those credits are temporary, and the long-term logic is now set: usage drives cost.
The bigger trend: AI pricing is moving from flat to dynamic
This isn’t happening in a vacuum.. The industry trend is clear: many AI services are shifting away from simpler. predictable pricing toward models that more directly reflect compute usage.. As agents become more common—especially those that run longer tasks—token-based or usage-linked billing becomes the closest match to what providers pay in infrastructure.
The tension for users is equally predictable.. Developers want affordability and predictability, but they also want assistants that work harder on their behalf.. GitHub’s line is that agentic usage is now default behavior. which increases inference demands; pricing needs to reflect that reality so the service remains reliable over time.
What to do if you rely on Copilot for heavy workflows
If your team uses Copilot mainly for quick completions, the change may feel modest. If you depend on longer coding sessions, repository-wide edits, or multi-step autonomous assistance, you’ll want to treat credits like a budget line—something you plan, monitor, and manage.
The most immediate action is to watch the bill preview when it appears in early May and align your workflows with the features that consume credits most heavily. In practice, that may mean setting expectations for when agentic sessions are appropriate, and when shorter, interactive usage is enough.
Over the next year. the likely outcome is that teams will become more intentional about how they “run AI.” In the same way companies learned to govern cloud spend. they’ll likely apply governance to AI usage—down to the coding habits that accidentally trigger high token runs.. Misryoum will be watching how teams adapt as Copilot’s pricing model moves from PRUs to tokens on June 1, 2026.