GitHub Copilot Officially Switches to Usage-Based Billing Starting June 1

As previously leaked, On Monday, GitHub announced a major change as to how Copilot will be priced and billed, moving the product away from its current request-based model toward full usage-based billing starting June 1, 2026.

At its core, the change replaces premium request limits with a monthly allocation of GitHub AI Credits across all Copilot plans. Rather than counting interactions, usage will now be measured through token consumption, including input, output, and cached tokens, based on model-specific API rates.

Copilot moves to usage-based billing model

In the announcement post, GitHub says the change reflects how Copilot has evolved beyond a simple coding assistant into a more agentic system that can handle long, multi-step development tasks. In this setup, usage is no longer uniform, since a quick prompt and an extended autonomous coding session no longer carry the same compute cost.

That being said, pricing tiers themselves are not changing. Copilot Pro stays at $10 per month, Pro+ at $39, Business at $19 per user, and Enterprise at $39 per user, with each plan receiving equivalent monthly AI Credit allocations.

Code completions and next edit suggestions will remain included without consuming credits, while heavier workloads will draw from the new credit pool. GitHub also confirmed that Copilot code review will now consume both AI Credits and GitHub Actions minutes.

Transition period and preview billing rollout

To ease the transition, GitHub will introduce a preview billing experience in early May, allowing users and admins to track projected usage before the full rollout in June. This will be accessible through the Billing Overview page on GitHub. Not to forget, GitHub is also removing fallback models once credits are exhausted, replacing them with budget-based controls instead.

For individual users, Pro and Pro+ plans will include credits equal to their subscription value, while annual subscribers will temporarily remain on the current system before migrating later. Businesses and enterprises will also receive pooled usage, allowing unused credits to be shared across teams rather than locked per user.

Moreover, admins will get better control over spending limits, with options to cap or allow overages depending on organizational needs.