GitHub Copilot moves to metered billing

GitHub Copilot is turning into a metered service. That’s the real story here. Starting June 1, 2026, GitHub will stop counting “premium requests” and start charging Copilot usage through GitHub AI Credits tied to token consumption. The base subscription prices stay the same, but the economics change a lot — especially for people using newer agent-style workflows that burn far more compute than old autocomplete ever did. ### What actually changed? GitHub said every Copilot plan will move to usage-based billing on June 1. Instead of a bucket of premium requests, users get a monthly allotment of GitHub AI Credits. Paid plans can buy more when they run out. GitHub also said usage will be calculated from input, output, and cached tokens using listed API rates for each model. ### Why ditch premium requests? Because one “request” stopped meaning anything consistent. A quick chat answer and a long autonomous coding session could both look like one unit to the user, even though the compute cost behind them was wildly different. GitHub basically admitted the old model no longer matched how Copilot works now that it includes cloud agents, code review, and heavier multi-step tasks. ### Are prices going up? Not in the obvious sticker-price way. GitHub says Copilot Pro stays at $10 a month, Pro+ stays at $39, Business stays at $19 per user, and Enterprise stays at $39 per user. But those prices now include a same-dollar monthly credit allowance, so the practical question becomes how fast your workflows consume credits — not just what plan you picked. ### Who feels this first? Heavy users. Inline code completions and Next Edit Suggestions remain included and do not consume AI Credits, which softens the blow for ordinary autocomplete use. But chat with expensive models, agent runs, and other compute-hungry features will now hit a visible meter. That means casual users may barely notice, while power users suddenly have to think about burn rate. ### What about annual subscribers? They get a temporary carveout. GitHub’s docs say Copilot Pro and Pro+ users who stay on existing annual billing plans remain on the request-based model until those plans expire, though model multipliers will change starting June 1. Monthly subscribers move automatically to usage-based billing on June 1. So the transition is immediate for some people and delayed for others. ### What changes for companies? This is where the shift looks most like cloud billing. GitHub says Business and Enterprise customers will get pooled usage, so unused credits from one person can help cover another. Admins also get budget controls at the enterprise, cost-center, and user levels, with the option to allow overages at public rate through June, July, and August 2026 to ease the switch. ### Is there another catch? Yes — Copilot code review gets billed twice in a sense. GitHub said code review usage will consume AI Credits and also GitHub Actions minutes, because that feature runs on GitHub-hosted runners unless customers use self-hosted infrastructure. So some “Copilot” activity now clearly behaves like infrastructure, not just software licensing. ### Bottom line? GitHub isn’t just tweaking a pricing page. It’s redefining Copilot as a metered compute product. That makes the service more sustainable for GitHub, but it also means developers and engineering managers now have to treat AI coding help the way they treat cloud spend — useful, scalable, and suddenly very measurable.