GitHub Copilot’s token billing sparks developer backlash
▼ Summary
– Microsoft is switching GitHub Copilot from a flat subscription fee to a token-usage billing model starting June 1, potentially raising costs significantly for smaller companies and workers.
– Some developers report drastic cost increases, with one user claiming their monthly bill would rise from $29 to nearly $750 under the new system.
– Critics argue that users experiencing extreme cost hikes are “vibe-coders” with little development knowledge who waste tokens on bloated iterations.
– Other users defend the change, noting that Copilot remains affordable for small outfits when used efficiently as a tool.
– Some online voices blame Microsoft for encouraging indiscriminate use of the chatbot and then suddenly changing the billing model, pulling the rug out from users.
The era of affordable, flat-rate GitHub Copilot access for individual developers and small teams is coming to an abrupt end. Microsoft is overhauling its billing structure, moving from a simple subscription fee to a token-usage model that could dramatically increase costs for heavy users. While large enterprises may absorb the change without much pain, smaller shops and independent coders are bracing for a serious hit to their monthly budgets.
Starting June 1, users will be charged based on the number of tokens consumed during their workflow, rather than a predictable flat fee tied to requests. This shift has sparked widespread frustration among developers who now face what they describe as a staggering price hike.
Social media platforms like Reddit and X have become hubs for this backlash. One Reddit user claimed their monthly bill would jump from roughly $29 to nearly $750 under the new system. “What a joke,” they wrote. “This new usage model is just stupidly expensive. I’m adjusting mine by cancelling. At that cost, it is no longer cost-effective or useful in any practical way.”
Another developer shared a screenshot showing their costs skyrocketing from about $50 to approximately $3,000, captioning it with “WOW, didn’t expect new pricing model to be this ridiculous.”
Not everyone is sympathetic, however. Some experienced users argue that these eye-popping figures are the result of inefficient coding habits. They point the finger at so-called vibe coders , developers with limited technical knowledge who rely heavily on AI assistance without optimizing their token usage.
“The vast difference between some of us working all day and still barely having overage and then these screenshots. I struggle to believe it’s complexity differences in the workload,” one commenter noted. “The only way it gets crazy like that is if you are purely ‘vibe coding’ with a ton of bloated iterations. It’s pretty affordable for even small outfits if used as a tool, on pretty much any provider.”
Others have turned their attention to the questionable economics of the old model. “Holy fuck how much money was copilot losing,” one Redditor asked, echoing a sentiment that many have quietly wondered about for years.
That question cuts to the heart of the matter. The financials behind GitHub Copilot have never been transparent. The scale of subsidies Microsoft likely provided to keep the flat-rate model viable , especially for users who treated the tool as an unlimited resource , remains a mystery.
Amid the debate, a third camp has emerged: those who argue that developers have a legitimate grievance. They contend that Microsoft actively encouraged users to lean heavily on Copilot, making it easier and more appealing to consume large numbers of tokens with each session. Now, the company appears to be changing the rules after the fact.
“To all the people blaming…the people who actually used the system the way that Microsoft built it (and even encouraged it to be used this way), honestly the only one at fault here is Microsoft,” wrote one frustrated user. “Microsoft provided this billing method and they kept making it easier and easier to burn through massive numbers of tokens on single premium requests that could churn for hours or even days while spawning dozens or even hundreds of sub-agents.”
TechCrunch reached out to Microsoft for comment but did not receive a response by press time.
(Source: TechCrunch)
