GitHub says all Copilot plans will move to usage-based billing on June 1, replacing premium requests with monthly GitHub AI Credits
Starting June 1, your Copilot usage will consume GitHub AI Credits. — TL;DR: Today, we are announcing that all GitHub Copilot plans will transition to usage-based billing on June 1, 2026.
The GitHub BlogMario Rodriguez
Context & Ripple Effects
GitHub had previously offered Copilot Enterprise as a per-user product and had signaled a later shift from request-based to token-based charging as operating costs rose. This announcement turns that direction into a dated, plan-wide migration centered on GitHub AI Credits.
The related coverage also places the billing change alongside GitHub’s desktop Copilot preview and agent-oriented canvases, making metered usage more consequential as Copilot expands beyond discrete code-completion requests.
First-order effects
Copilot customers on every plan must move from premium-request allowances to monthly AI Credits beginning June 1, making their bill and available usage directly dependent on consumption.
GitHub gains a pricing mechanism that more closely ties Copilot revenue to the cost of serving individual users and workloads.
Second-order effects
Teams using Copilot will need to monitor credit consumption and decide which workflows justify higher-cost AI use, especially as desktop and agent interactions can increase usage intensity.
Competing coding-assistant vendors face greater pressure to explain whether their own pricing offers more predictable spend or better value per useful task.
Third-order effects
If usage-based charging becomes standard for developer AI, software-seat budgeting will increasingly incorporate AI consumption controls rather than treating copilots as fixed-cost productivity add-ons.
The change points to an AI FinOps gap in developer tooling: adoption may depend not only on model capability, but on organizations’ ability to measure, allocate, and govern variable inference costs.
The trend: Developer AI is shifting from flat per-seat subscriptions toward pricing that passes through more of the underlying model-use cost to customers.
My prediction is that GitHub will move to usage based billing for all source control operations by the end of 2026. Copilot is just them trialing the billing infrastructure and market response.
I will totally need to reevaluate how I work with AI now But this makes a lot of sense, it is not really sustainable to manage economics when some people consume millions of tokens per single premium token Nevertheless it's hard to grok for anyone who got used to taking
Starting June 1st, GitHub Copilot will move to a usage-based billing model as GitHub Copilot supports more agentic and advanced workflows. In early May, you'll see a preview bill experience, giving visibility into projected costs before the transition. 👉 Read more about the
Its the beginning of the end of subsidized AI subscriptions. GH Copilot is moving to usage-based billing, as has Claude (for business customers.) Fair to assume more will follow. I expect this change will also be a great boost for open models - cheaper, and pretty good already
Copilot is going credit-based June 1. Pay per token, just like the API. Anyone reselling someone else's model was always going to end up here. You can't subsidize inference forever when you don't own the model. This is why local LLMs matter. Not because they're frontier — they're…
People love to say AI/LLMs are “here to stay” but they never really ever explain what that means. Like of course the tech will always exist but LLMs are largely expensive to run. What will AI look like when it's no longer subsidized? [embedded post]
GitHub Copilot is no longer absorbing as much of the cost of inference (inference got cheaper but you're doing more of it though not sure that's a Jevons quite yet) and I am absolutely wondering about the timing of this and the OpenAI divorce (although GitHub Copilot uses multipl…