Developers Voice Concerns Over GitHub Copilot’s New Token-Based Billing System

The golden age of Microsoft’s GitHub Copilot appears to be coming to an end, especially for independent users. The shift from a flat subscription model to a token-based billing system could result in significantly higher costs for many. While larger enterprises may adapt without issue, smaller businesses and freelancers may find it challenging to keep their monthly expenses in check.

Beginning June 1, billing will be determined by token consumption rather than a fixed fee for requests.

Developers with budget concerns have taken to platforms like Reddit and X to express their worries about what they see as a dramatic increase in costs.

“What a joke,” a Reddit user remarked, noting that their monthly payment of about $29 could escalate to nearly $750 under the new pricing model. “This usage model is just absurdly expensive. I’m considering cancellation; it’s no longer practical or affordable.”

Another user responded, “WOW, I didn’t expect the new pricing model to be this outrageous,” sharing a screenshot that showed their costs skyrocketing from around $50 to nearly $3,000.

While these increases may seem excessive, some Copilot users have defended the pricing changes, arguing that experienced users shouldn’t typically use tokens at such a fast rate. Critics suggest that those who spend heavily may be less experienced developers focused on “vibe coding.”

“It’s hard to believe these screenshots represent differences in workload complexity,” one user commented. “The only way costs get so high is if you’re relying on ‘vibe coding’ with unnecessary iterations. When used properly, it remains cost-effective for even small teams.”

Others have questioned the financial sustainability of the old model. “How much money was Copilot losing?” one Reddit user asked in a recent discussion.

It’s a fair question.

The financial aspects of Copilot have often been unclear, and the extent of the company’s spending to support extensive platform usage remains uncertain.

As some criticize the new pricing and others debate the validity of those critiques, numerous voices online contend that developers have legitimate grounds for dissatisfaction, given that Microsoft encouraged intensive use of its chatbot and now seems to be retracting support.

“To those blaming users for utilizing the system as Microsoft intended (and even promoted), the responsibility lies with Microsoft. They created this billing structure and made it increasingly easy to exhaust large amounts of tokens on single premium requests that could last for hours or even days, generating numerous sub-agents,” one user posted.

TechCrunch reached out to Microsoft for comments but did not receive a response prior to publication.