GitHub Copilot is ditching its predictable monthly pricing for token-based billing, and developers are calling it exactly what it is: a price increase dressed up as flexibility.

The change means you’ll now pay based on how many tokens Copilot processes, not a flat fee. For anyone who’s used ChatGPT or Claude’s API, you know how this works. For everyone else, tokens are roughly equivalent to syllables or chunks of text. Generate a lot of code? You’ll burn through tokens fast.

Microsoft hasn’t announced specific pricing yet, but the developer response on forums and social media has been overwhelmingly negative. The complaints break down into a few camps: people who liked the predictability of a flat fee, people who think this is clearly just a way to extract more money from power users, and people who are now doing mental math every time they hit tab to accept a suggestion.

Why This Matters

Copilot has been one of the most successful AI coding tools precisely because it didn’t make you think about cost. You paid your monthly fee (currently $10 for individuals, $19 for business users), and you used it however much you wanted. That’s a big deal when you’re learning a new framework or working through a tricky problem and generating dozens of suggestions per hour.

Token-based billing changes that psychology. Now there’s a meter running. For solo developers and small teams, that might mean second-guessing whether to use Copilot for boilerplate code or simple refactoring. For larger companies, it means finance teams are going to want usage reports and spending caps.

The timing is also interesting. Copilot launched in 2021 as one of the first mainstream AI coding assistants. It’s had the market mostly to itself for years. But now there’s real competition: Cursor, Cody, Tabnine, and a dozen other tools are all fighting for the same developers. A surprise price increase, even one that Microsoft will surely frame as “usage-based flexibility,” is a good way to lose sticky users who were already eyeing the exit.

What Developers Are Saying

The Hacker News thread is full of people running cost projections and coming up with numbers that are multiples of their current bills. One comment that keeps getting upvoted: “What a joke.” Another user pointed out that if you’re a heavy Copilot user who relies on it for most of your coding, you might end up paying $50 or $100 a month under the new model. That’s speculation until Microsoft releases actual pricing, but it’s not unreasonable speculation.

There’s also frustration that this feels like classic enterprise software bait-and-switch. Get people hooked on a flat fee, then move to consumption pricing once they can’t imagine working without it. It’s the SaaS playbook, and it works, but that doesn’t mean people have to like it.

Who Should Care

If you use Copilot daily, you should absolutely care. Start tracking how much you actually use it, because you’re about to be paying by the token. If you’re evaluating AI coding tools and were leaning toward Copilot because of its stable pricing, well, that advantage just evaporated.

If you’re a manager or founder who pays for Copilot seats for your team, get ready to have budget conversations. You’ll want to understand the new pricing before it kicks in, and you might want to look at alternatives while you’re at it.

The Bigger Picture

This isn’t just about GitHub. Token-based billing is becoming the default for AI tools, and it makes sense from a provider’s perspective. Inference costs scale with usage, so charging by usage aligns incentives. But flat-fee pricing has been a huge unlock for developers who want to experiment and learn without worrying about the bill. Losing that is a step backward.

Microsoft will likely argue that light users will pay less under the new model. That might even be true. But the people who get the most value out of Copilot, the ones who use it constantly, are the ones who are about to pay a lot more. And those are the people who are most vocal online, which is why the backlash is so loud.

The new pricing hasn’t rolled out yet, so there’s still time for Microsoft to adjust course or at least release details that make this less painful than it looks. But right now, this feels like a miscalculation. Developers have options, and they’re not shy about switching tools when the value proposition changes.