Published: June 1, 2026 | Reading time: 6 minutes
Starting today, GitHub Copilot no longer works the way millions of developers signed up for. Microsoft has officially flipped the switch on a new token-based billing model for its AI coding assistant — replacing the predictable flat-rate subscription that made Copilot one of the most widely adopted developer tools on the planet.
The backlash has been immediate, loud, and in some cases, financially alarming.
What Changed?
Until today, Copilot subscribers paid a simple monthly fee and got a set number of “premium requests” — a straightforward model that made budgeting easy. When you ran out of premium requests, Copilot fell back to a cheaper model so you could keep working.
That safety net is now gone.
GitHub has replaced premium requests with a new unit called GitHub AI Credits, which are consumed based on actual token usage — meaning every word the model reads and generates costs you something. Once your monthly credits run out, premium features stop working until your next billing cycle.
Base subscription prices haven’t changed on paper:
- Copilot Pro: $10/month
- Copilot Pro+: $39/month
- Business: $19/user/month
- Enterprise: $39/user/month
But those prices now represent a credit allowance, not a ceiling. Heavy users — particularly those running agentic coding sessions, using Copilot Chat extensively, or triggering code reviews — will burn through that allowance and face additional charges.
How Bad Can It Get?
For some developers, very bad. Reactions on Reddit and X have ranged from disbelief to outrage, with several users sharing screenshots of projected cost increases that are hard to ignore.
One developer said their monthly bill was set to jump from $29 to nearly $750. Another shared a projection showing costs going from $50 to around $3,000. These are outliers, but they illustrate the ceiling that no longer exists.
GitHub’s Chief Product Officer Mario Rodriguez acknowledged the shift directly in the announcement, stating that Copilot is simply not the same product it was a year ago. The tool now powers complex, multi-step agentic workflows that consume far more compute — and GitHub says the old pricing model was no longer sustainable.
There’s some truth to that. The economics behind Copilot’s flat-rate pricing were always opaque. A developer running an agentic session for hours, spawning dozens of sub-agents across a large codebase, was consuming an enormous amount of compute for $10 or $39 a month. Someone was subsidising that — and it appears that arrangement is now over.
Not Everyone Is Unhappy
Not all developers are sounding the alarm. A vocal contingent has pushed back on the horror stories, arguing that the projected cost spikes are almost exclusively a “vibe coding” problem.
The argument goes like this: a developer who understands their tools and uses Copilot with intention — reviewing suggestions, not just blindly accepting rewrites — will barely notice the change. The people seeing $3,000 bills are those who have been asking the model to rewrite entire codebases on a loop, burning through massive context windows without much to show for it.
There is a reasonable point buried in that critique. Token-based billing does expose wasteful usage in a way flat pricing never did.
But critics of that argument point out that Microsoft built and aggressively marketed Copilot as a tool designed to encourage exactly that kind of usage. Agentic coding, long sessions, iterative rewrites — these weren’t edge cases. They were features. Pulling the financial rug from under users who adopted the product in good faith is a harder pill to swallow.
What GitHub Is Doing to Ease the Transition
To soften the blow, GitHub is offering promotional credits for June, July, and August:
- Business customers ($19/month) receive an extra $30 in credits per month
- Enterprise customers ($39/month) receive an extra $70 in credits per month
For organisations, GitHub is also introducing pooled usage — unused credits from lighter users can offset heavier users within the same billing account. That’s a meaningful feature for teams with mixed usage patterns.
Administrators can now set budget caps to prevent runaway costs, and individual users will need to pay closer attention to their usage dashboard than ever before.
Annual plan subscribers keep the old billing model until their current term expires, at which point they’ll move to monthly usage-based billing.
The Bigger Picture
GitHub Copilot is a product that grew from a novelty to a genuine part of daily developer workflows in just a few years. Microsoft reported that GitHub surpassed $2 billion in annual recurring revenue, with Copilot as a primary growth driver. That success has apparently created a different kind of pressure — the need to make the product financially sustainable at scale.
What’s happening to Copilot is part of a broader industry shift. OpenAI, Anthropic, and Google all charge API customers based on token consumption. Applying that model to a consumer-facing developer subscription is newer territory, and the friction shows.
The real test will come in July, when the promotional credits expire and developers see their first fully organic usage-based bills. If the numbers are manageable for most users, the noise will likely fade. If they aren’t, Microsoft may be handing competitors like Cursor, Windsurf, and direct API integrations a very compelling talking point.
Should You Stay or Switch?
If you’re a light-to-moderate Copilot user — using it primarily for code completions and occasional chat — your costs will likely stay similar to what you’ve been paying.
If you run frequent agentic sessions, use Copilot Chat heavily throughout the day, or rely on Copilot for automated code reviews, it’s worth auditing your usage now before next month’s bill arrives. GitHub has made usage dashboards available so you can get a sense of where you stand.
For developers already considering alternatives, this is a natural moment to evaluate options. We’ll be covering the best GitHub Copilot alternatives in a follow-up piece shortly.
Sources: GitHub Blog, TechCrunch, Visual Studio Magazine, GitHub Community Discussion #192948