GitHub Copilot’s new token-based billing is not just a pricing tweak — it is a philosophical rewrite of the product. What used to feel like a mostly predictable developer subscription is becoming a compute meter, and that is exactly why so many developers are furious.
<> The real backlash is not about a few extra dollars. It is about GitHub replacing a simple mental model with a bill that can move every time your prompt gets longer./>
Starting June 1, 2026, GitHub will replace premium request units with GitHub AI Credits, and those credits will be consumed based on token usage. GitHub says this applies across its Copilot lineup, with code completions and Next Edit suggestions remaining included, while most other features are metered. The company’s own explanation is straightforward: Copilot has evolved into a more complex, agentic product, and pricing should reflect actual usage and underlying costs.
That is defensible on paper. In practice, it is the kind of change that makes developers reach for calculators, dashboards, and profanity.
The problem is not that usage-based pricing is inherently evil. Cloud software has been living this way for years. The problem is that Copilot sold itself as the easy AI coding tool: one seat, one bill, one rough sense of value. Token billing destroys that illusion. Now prompt length, output length, context windows, and agentic workflows all matter directly to spend. For heavy users, that is not a minor adjustment. It is a complete rethinking of how you budget for code generation.
<> This is the classic enterprise AI trap: the more useful the tool gets, the harder it is to predict what it will cost./>
GitHub is trying to soften the blow with budget controls, usage previews, and visibility in the editor and admin dashboards. But visibility is not the same thing as simplicity. A dashboard that shows you your burn rate does not make the burn rate easier to tolerate. It just helps you watch the meter spin.
The rollout also has the unmistakable smell of a transition that benefits the vendor more than the user. Annual Pro and Pro+ subscribers stay on the older model until their terms end, but they will not auto-renew under it. GitHub has also paused self-serve Copilot Business purchases and made temporary changes to individual plans while preparing the broader shift. That is not the behavior of a company merely “updating” pricing. It is the behavior of a company preparing users for a new normal.
- What changes: request-based pricing gives way to token-based credits.
- What stays included: code completions and Next Edit suggestions.
- What gets riskier: long prompts, bigger contexts, and agent-style workflows.
- What users lose: predictable per-seat cost and the feeling that Copilot is “just included.”
The harshest criticism, though, is not technical. It is trust-based. Developers do not mind paying for value; they mind being told yesterday’s bundle is today’s meter.
GitHub may be right that the old model no longer fits the product it has built. But the company should not be surprised that developers see this as a downgrade in disguise. When your pricing model starts looking like a cloud invoice instead of a product plan, you should expect customers to stop calling it convenience and start calling it exposure.
