GitHub Copilot users report massive bill increases after Microsoft switches to token-based pricing
Microsoft will switch GitHub Copilot to a token-based pricing model starting June 1, prompting reports from developers that their monthly bills could surge from $29 to as high as $750 or $3,000 due to increased token consumption. Critics argue the shift undermines affordability and predictability, while Microsoft frames it as a more usage-aligned approach, though concerns persist over transparency and cost control.
Microsoft announced it will transition GitHub Copilot to a token-based pricing model on June 1, replacing the current flat-rate subscription. Developers have expressed alarm over potential cost spikes, with some reporting estimated monthly bills jumping from $29 to nearly $750 or even $3,000, based on token usage during coding sessions. The change shifts pricing from a fixed fee to a variable model, where every interaction—such as code generation or debugging—consumes tokens, directly impacting costs. While Microsoft describes this as a fairer, usage-based approach, developers criticize the lack of predictability, particularly for independent users and small teams relying on AI-assisted workflows. Early reactions on platforms like Reddit and X highlight frustration, with users sharing screenshots claiming extreme bill increases. One developer noted their current $29 plan could rise to $750, calling the new model 'ridiculously expensive.' Others argue such spikes may stem from inefficient prompting rather than typical usage, though skepticism remains about Microsoft’s transparency. The pricing shift has also reignited debates over Copilot’s past affordability, with some suggesting Microsoft subsidized early adoption to drive usage before scaling costs. Critics accuse the company of altering billing rules after developers built workflows around flexible, low-cost access, effectively 'changing the rules' post-adoption. Microsoft has not provided detailed breakdowns of token consumption or pricing tiers, leaving developers uncertain about how to manage costs. The transition raises broader questions about the sustainability of AI tools in professional workflows, especially for smaller teams with limited budgets. As the June 1 deadline approaches, developers are weighing whether to continue using Copilot under the new model or seek alternatives to avoid unexpected financial strain.
This content was automatically generated and/or translated by AI. It may contain inaccuracies. Please refer to the original sources for verification.