Starting June 1, GitHub Copilot stopped being a predictable flat-rate subscription. Microsoft flipped the switch today, moving all Copilot plans from premium request units to token-metered "AI Credits." The headline prices haven't changed — Pro is still $10/month, Business is still $19/user — but what those dollars actually buy has changed fundamentally.
This isn't abstract. Within hours of the cutover, the official GitHub community announcement thread hit 900 downvotes and 400 comments. TechCrunch ran their coverage under the headline "What a joke." Developers are projecting cost jumps from $29/month to $750, and from $50/month to $3,000 — not for enterprise teams, but for individual heavy users who took Copilot seriously as an agentic tool.
Here's the math that matters: one AI Credit = $0.01. A Pro plan includes 1,000 credits ($10 worth). That sounds reasonable until you use agentic features — where Copilot plans, researches, and executes multi-step tasks across your codebase. A single agentic session can consume $30 to $40 in credits. Which means if you have a dev who runs two agent sessions a day, the Pro plan evaporates by Tuesday morning and you're in overage territory for the rest of the month.
Who Gets Hit Hardest
This doesn't hurt everyone equally. Light users — people mostly doing inline completions and occasional chat questions — will barely notice. Their usage probably fits within the included credits.
But if your team has started leaning on AI agents for real work, this is a different conversation. Agentic coding — having the AI plan and execute a multi-step refactor, write tests, update documentation, and open a PR — is where Copilot has been getting genuinely useful. It's also where token burn is highest, because those sessions use large context windows and multiple back-and-forth model calls.
The developers reporting $750/month projections aren't outliers. They're the early adopters who actually took Copilot seriously as a productivity multiplier. And now that they've built workflows around it, the pricing just changed underneath them.
This is the classic vendor lock-in pattern: build reliance on a tool at a predictable price, then change the pricing once switching costs are high.
The Small Org Risk Is Specifically Surprise Bills
Most small orgs don't have someone watching billing dashboards in real time. You put Copilot Business on a card at $19/user, set up six developers, and reasonably assume your cost is $114/month. Under the old model, it was.
Under the new model, if those developers are running agent sessions against large codebases, your actual bill at month end could be multiples of that. The credits included with each plan run out, and then you're charged for actual consumption. GitHub hasn't published a clear hard cap or a simple projected cost calculator — the community is doing that math manually in forum comments right now.
The advice to "just monitor usage" is reasonable if you have a dedicated DevOps engineer watching dashboards. Most 6-person dev teams don't. Most 3-person NGO IT shops definitely don't.
What the Alternatives Actually Look Like
The developer community is already voting with its feet. Here's what the realistic options look like right now:
Continue.dev + direct API — Continue is an open-source VS Code and JetBrains extension (Apache 2.0, zero cost). You wire it to whatever API you prefer: DeepSeek V4 (now permanently discounted and extremely capable for code), Mistral Medium 3.5, or a locally-run model via Ollama. You pay only for what you use at raw API rates, with complete billing visibility and no subscription layer. For teams comfortable with a modest setup step, this almost always costs less than metered Copilot once agentic work enters the picture.
Cline — Another open-source VS Code extension that's been popular on r/LocalLLaMA for the past six months. Same model: connect your own API keys, pay only token costs. Works well with multiple providers and lets you switch models mid-project.
Aider — CLI-based coding agent, Apache 2.0 license, no subscription. A lot of power users doing complex refactors live here. Their monthly AI spend is a fraction of what equivalent Copilot agentic work would now cost.
Cursor — If you want a polished, managed experience rather than DIY, Cursor Pro is $20/month with a more straightforward cost model. Developers switching from Copilot to Cursor are generally reporting better predictability, even though it's not free.
For orgs using Copilot for completions only and not agents: you're probably fine staying put. But if agentic workflows have become part of how your team operates — and for a lot of teams that happened quietly over the last year — the calculus just changed.
What To Do This Week
Audit who uses what features. The billing exposure is almost entirely in agentic and agent-mode sessions. Inline completions are comparatively cheap. Find out which of your developers are running agent sessions, and how often.
Set billing alerts now. GitHub does support usage notifications. Configure one at 50% of included credits and one at 80%, so you're not discovering the overrun on invoice day. Takes five minutes, prevents a bad conversation with your finance person.
Pilot a BYO-LLM setup. Continue.dev plus a DeepSeek or Mistral API key takes about 20 minutes to configure. Pick one developer, run it for a week alongside their existing workflow, and compare actual costs. You'll have real numbers to evaluate instead of projections.
Hold off on expanding Copilot seats. If you were planning to add more developers to Copilot Business, pause. Expand the pilot to two or three people first and watch the billing through one full month under the new model before committing to more seats.
The community anger here is partly about the substance — real cost increases for real workflows — and partly about how this was communicated. The token pricing isn't published in a way that makes it easy to project real monthly costs before you've already got half your team using agentic features. People are doing the math in real time and not liking it.
Small orgs need predictable AI spend. The tools to get that predictability exist right now — open-source, self-hosted or API-direct, with billing you can actually understand. The question is whether you get ahead of this before the surprise invoice, or after.
We help teams audit their AI tool stack and set up workflows that don't create budget surprises — usually in a single sprint. If you're sorting through this today, we've worked through exactly this situation with other clients. No long-term commitment required.