Microsoft’s GitHub Copilot is shifting to a token-usage billing system that will significantly increase costs for users, according to TechCrunch. The new pricing model will go into effect on June 1, 2026, leaving many developers concerned about budget implications.
What happened
Starting June 1, GitHub Copilot will transition from a flat subscription rate to a token-based payment system. Users will be charged based on the number of tokens they utilize while coding, marking a departure from the previous low monthly fee. Many developers expressed shock at the potential cost increases, with some noting a jump from approximately $29 per month to nearly $750.
One user lamented, “This new usage model is just stupidly expensive. I’m adjusting mine by cancelling.” Another reported a staggering increase from around $50 to approximately $3,000 due to the new billing structure. While some users criticized the model, others defended it, suggesting that those facing exorbitant charges lacked experience in efficient coding practices.
“The only way it gets crazy like that is if you are purely ‘vibe coding’ with a ton of bloated iterations,” noted one user.
Why it matters
This shift could have significant financial implications for smaller businesses and individual developers who rely on GitHub Copilot. The traditional model, which encouraged regular usage, is giving way to a pricing structure that could strain budgets. Developers worry that the new costs may deter their ability to effectively utilize the tool.
A prevailing sentiment in the developer community is that Microsoft’s changes undermine the usage patterns cultivated under the previous flat rate system, creating a backlash against the company for what some view as misleading practices.
Background
The announcement follows a growing trend among tech companies to adopt usage-based billing systems. On May 20, 2026, Microsoft revealed its plans for the switch, citing the need to better align usage with pricing. The previous flat rate, perceived as unsustainable by some developers, has prompted questions about the financial viability of the service.
Feedback from the developer community has varied, with some users calling for a return to the old pricing model. Many question how the transition will affect their ability to incorporate AI tools in their daily work.
What’s next
As the June 1 implementation date approaches, developers are encouraged to reassess their usage and costs associated with GitHub Copilot. Microsoft has yet to provide further clarification on the changes but will likely face continued scrutiny from users regarding the economic implications of the new billing model.
