By ByteBot
GitHub Copilot flips to usage-based billing on June 1, 2026. Your subscription price stays the same — $10 for Pro, $19 for Business — but the value underneath it is changing. Premium Request Units are out. GitHub AI Credits are in. And two days after the announcement, Microsoft quietly shipped token-reduction features in VS Code. That reaction says more than the press release ever will.
What’s Actually Changing
The new system prices Copilot usage by token consumption. Every chat message, every agent action, every code review burns through your monthly credit allotment. The key distinction: code completions and Next Edit suggestions stay free, unchanged for all plans. Everything else is now metered.
That “everything else” list is long: Copilot Chat, the CLI, the cloud agent, Copilot Spaces, code review, Spark, and third-party agents. If you use Copilot the way GitHub has been encouraging you to — with agents, in workflows, reviewing PRs automatically — you are now in metered territory.
Code review has a particularly nasty wrinkle: it gets billed twice. Token consumption draws from your AI Credits. The agentic runner infrastructure that powers the review eats GitHub Actions minutes separately. One feature, two meters running simultaneously. GitHub confirmed this in its April changelog.
The Numbers
Each plan receives AI Credits equal to its monthly dollar cost — a 1:1 ratio. Copilot Pro ($10/month) gets roughly 1,000 credits. Copilot Business ($19/user/month) gets around 1,900. Enterprise ($39/user/month) gets 3,900. One credit equals one cent.
| Plan | Monthly Price | AI Credits Included |
|---|---|---|
| Copilot Pro | $10/user | ~1,000 credits |
| Copilot Pro+ | $39/user | ~3,900 credits |
| Copilot Business | $19/user | ~1,900 credits |
| Copilot Enterprise | $39/user | ~3,900 credits |
A developer actively using Copilot Chat for debugging, running automated code reviews on open PRs, and working in a Copilot Spaces session can realistically burn 200 to 750 credits per day. At the high end, a Pro subscriber hits their monthly credit ceiling in roughly 36 hours of work. Not 36 hours of heavy usage — just 36 hours at the desk with agentic features turned on.
There is a temporary reprieve: from June through August 2026, Business users get $30/user in credits and Enterprise gets $70/user. After August, the promotional cushion disappears and the 1:1 ratio locks in permanently.
Microsoft’s Tell
On April 29 — exactly two days after GitHub announced the billing change — VS Code 1.118 shipped with a notably specific set of improvements: deferred tool loading that caps the always-available agent tool schema at roughly 30 core tools, smarter prompt caching, and purpose-built smaller models for search and execution tasks. The release notes quantify up to 20% token savings in agent mode.
Microsoft built token-efficiency features into its own IDE within 48 hours of announcing the pricing change. That is not a coincidence. Visual Studio Magazine covered the timing explicitly. It is an acknowledgment that the new billing model will increase costs for active users, and that Microsoft knows it.
The Backlash
GitHub’s community FAQ discussion for the billing announcement grew from 70 comments to 237 comments and 319 replies in three days. The most-shared line among developers: “You will get less, but pay the same price.”
The complaints are concrete. Developers want to know if unused credits roll over (GitHub has not confirmed this). They want clarity on annual plan treatment mid-cycle. They want to understand how many credits a typical agent session actually costs before committing to the new model. Visual Studio Magazine documented the developer backlash in detail.
None of this is surprising in context: GitHub had previously halted new Copilot signups entirely due to “soaring usage and rising costs.” The flat-rate model was described as “currently unsustainable.” Usage-based billing is not a financial feature — it is a financial corrective that transfers cost risk from GitHub to developers.
What to Do Before June 1
GitHub released April usage reports on May 12. They are available now in the GitHub admin and organization billing dashboards. This is the only real data available to model what June looks like. Pull them before the switch.
- For teams: Identify which developers rely on agentic features, Copilot Spaces, and automated code review. Those users will hit credit limits first. Set a monthly spending cap in GitHub’s billing settings before June 1.
- For individuals: Consider whether $10/month Copilot Pro still competes with Windsurf Pro at $15/month or Cursor Pro at $20/month once the credit meter is running. The Copilot price advantage narrows considerably when chat and agents start drawing down a finite pool.
- For everyone: Read GitHub’s official preparation guide and set spending alerts in billing settings now.
The Bigger Picture
GitHub Copilot is not alone. The flat-rate AI tooling era — built during 2023-2025 to acquire users at below-cost pricing — is ending. Every AI product that promised “unlimited” is now walking it back. Copilot is just the most visible because it has the most enterprise users and the deepest workflow integration.
The deeper irony: the tighter your GitHub integration, the higher your new bill. The developers who went all-in on Copilot in their workflows — reviews, agents, Spaces — are exactly the users who will feel this most. Loyalty to the toolchain is now a cost center.
June 1 is two weeks away. The official billing announcement has the full details. The usage reports are out. Now is the time to check both.
