GitHub Copilot Kills Flat-Rate Billing June 1. Your $10/Month Now Has a Cap.

$10 a month. That's what you pay for Copilot Pro. As of June 1, that's also exactly what you get in tokens. Not unlimited completions. Not a comfortable buffer.

exactly ten dollars worth, and when it's gone, the assistant stops working mid-project.

GitHub flipped the switch on usage-based billing April 27.

annual plans retire. Free fallback models vanish. Model multipliers spike. One afternoon of agentic coding burns through what used to be a month's budget. This isn't a pricing tweak. It's a structural reset. And if you're on Copilot today and didn't read the fine print, you're about to get a rude surprise.

The Multipliers Are the Story

Here's the part everyone's skipping.

Claude Opus 4.7 goes from 7.5x to 27x.

Same credits, 27 times less compute. GPT-5.4 goes from 1x to 6x. GPT-4.1, which was free until now, costs 1x. If you've been defaulting to GPT-4.1 because you thought it was bundled, you're burning credits you never tracked. The model you thought was free is eating your budget right now, and you didn't even notice.

annual subscribers get the worst version of this. You stay on old PRU pricing until your term ends, but the multipliers spike June 1 regardless. Your annual plan buys you less compute without your monthly cost changing. When the term expires, you drop to Copilot Free. No warning. No graceful transition. Just no Copilot.

Who's Getting Screwed

The three-month buffer GitHub gave Business and Enterprise looks generous until you read what it actually is. Business gets $30 in credits through August instead of $19. Enterprise gets $70 instead of $39. That's not a gift.

That's GitHub admitting the new numbers are too harsh to roll out cold, so they're staggering the pain.

For solo devs and small shops on monthly plans, you at least know the number. The problem is nobody's published what a typical session actually costs in the new system. You won't know if $10 is enough until you're three hours into a feature and the meter hits zero. That's not a billing model.

That's a trap.

Three Things to Do Before June 1

Check your current credit usage this week.

Before the new system kicks in, pull your history and see what you're actually burning. You need a baseline to compare against.

Then map your model stack. Which tasks need GPT-5.4. Which need Claude. Which can you run on the free tier without hating the results.

The days of picking the best model for everything since the subscription covers it are done.

If you're on an annual plan, check the expiration date.

If it's after June 1, you're already on the transition clock. Your credits shrink every month until the term ends and you fall off the cliff to Copilot Free.

The teams that audit this before June 1 won't get surprised mid-project. The ones who don't will be the ones posting on HN asking why their credits ran out in the middle of a deploy.

---

Sources

- GitHub Official. Copilot Moving to Usage-Based Billing - Hacker News. Copilot Usage-Based Discussion - ZDNet. GitHub Copilot Shifts to Usage-Based Pricing - ChatAI — Annual Copilot Subscribers Face June 1 Deadline