GitHub Copilot is moving from a flat subscription to token-based billing on June 1, and developers online are reacting with fear and fury—citing dramatic price jumps from roughly $29 to as much as $750 a month, and even screenshots showing increases from about
By the time June 1 hits. some developers will be staring at a new number on their Copilot bills—and they don’t like what it might mean for every month after. GitHub’s shift from a flat subscription rate to a token-usage system replaces a predictable cost with one that tracks how many tokens users burn through while they work.
The change is straightforward on paper: users will be charged based on token consumption instead of a low flat rate based on requests. For smaller companies and individual workers who have been budgeting around that earlier model, the move has landed like a sudden tax on the way they code with AI.
Online, frustration has turned personal and immediate. One Redditor. writing “What a joke. ” said their current cost of about $29 per month could balloon to nearly $750 a month under the new system. They added that the usage model is “stupidly expensive. ” and said they were “adjusting mine by cancelling. ” arguing that at that price it’s no longer cost-effective or useful.
Another developer posted a screenshot they said showed costs jumping from around $50 to some $3,000. The increases sound extreme to the people sharing them, but the reaction isn’t one-note.
Several Copilot users pushed back. arguing that those price shock stories come from how the tool was used rather than from the billing model alone. One critic said that the “vast difference between some of us working all day and still barely having overage and then these screenshots” doesn’t make sense if workloads are truly similar. They wrote that they struggle to believe it’s complexity differences in the work. adding that the only way costs get that high is if users are essentially “vibe coding” with “a ton of bloated iterations.”.
That same user also said Copilot is “pretty affordable for even small outfits if used as a tool,” and argued it remains practical “on pretty much any provider.”
As the debate churned, some people focused less on individual screenshots and more on the economics of the prior billing approach. “Holy fuck how much money was copilot losing,” one Redditor asked.
That question hangs over the current outcry because the real mechanics of Copilot’s cost structure—and what the company may have been subsidizing—have never been fully visible to the public. What developers can see, however, is a new way they may be asked to pay.
There’s also a harder layer to the argument: some users say Microsoft effectively invited the behavior that now seems to be getting punished. One developer wrote that “the only one at fault here is Microsoft. ” saying the company encouraged users to use its chatbot indiscriminately and then appears to “pull[] the rug out” after people adopted the workflow. They claimed Microsoft provided a billing method and “kept making it easier and easier to burn through massive numbers of tokens on single premium requests. ” describing scenarios where premium requests could churn for hours or even days while spawning dozens or even hundreds of sub-agents.
Microsoft was asked for comment, but did not respond by publication time.
The tension heading into June 1 is simple: Copilot’s usefulness for some depends on speed and iteration. while token-based billing turns that same behavior into a variable cost. For the people reporting drastic jumps. the tool has stopped feeling like software they can rely on and started feeling like a meter they can’t control.
GitHub Copilot token-based billing June 1 pricing change developer backlash software costs AI coding tools Microsoft