On April 27, 2026, GitHub announced that all Copilot plans are moving to usage-based billing on June 1, 2026. The flat "premium request" model is dead. Welcome to per-token pricing for AI coding assistants.

If you're a solo developer, this might not change much. If you run an engineering team, you need to read this carefully — because your AI bill is about to become unpredictable in ways it wasn't before.

Here's what's actually changing, why it's happening, and what you should do this month.

What's Changing

Today, Copilot uses Premium Request Units (PRUs). You get a monthly bucket of requests, and every chat or agent prompt counts as one — regardless of whether it's a one-line question or a 30-minute autonomous coding session.

Starting June 1, 2026:

• PRUs are replaced by GitHub AI Credits (1 credit = $0.01 USD)
• Every interaction is billed by token consumption — input + output + cached tokens
• Each model has its own per-token rate, matching published API rates
• Code completions and Next Edit suggestions remain free across all plans
• Plan base prices are unchanged: Pro $10/mo, Pro+ $39/mo, Business $19/seat, Enterprise $39/seat
• Each plan includes monthly AI Credits equal to its subscription price (Pro = $10 in credits, etc.)

The big shift: a quick question and a multi-hour agentic session no longer cost the same.

Why GitHub Did This

Read between the lines of the official announcement and the picture is clear. Agentic coding broke the math.

A single autonomous coding session — running across an entire repo, calling tools, iterating, retrying — can consume thousands of times more compute than a chat question. Under PRUs, both counted as "one request." A handful of power users can cost more than the plan price covers.

GitHub said it directly in their April 21 update on individual plans: "It's now common for a handful of requests to incur costs that exceed the plan price."

That's not sustainable. Token-based billing aligns price with cost. It's the same reason every API provider has always priced this way.

Who Wins, Who Loses

Wins: Developers who mostly use code completions and light chat. You'll likely see no real change. Your $10 Pro plan probably never came close to using $10 in tokens.

Loses: Heavy agent users. If you're running long-trajectory agentic workflows — multi-step refactors, autonomous bug-fixing across files, parallel subagents — you'll feel this. The same workflows that gave you outsized value under PRUs are exactly what's getting expensive.

Maybe: Teams. It depends entirely on how your developers actually use Copilot. Some companies will save money. Others will hit budget caps mid-month for the first time ever.

The Annual Plan Trap

If you're on an annual Pro or Pro+ plan, GitHub is doing something clever and slightly hostile: you keep your existing PRU-based pricing until the plan expires — but model multipliers go up on June 1 for annual subscribers only.

Translation: your existing annual plan gets quietly worse. You can either ride it out at degraded value, or convert to a monthly plan early and get prorated credit.

If you're an annual subscriber, you should sit down before June 1 and decide which path actually saves you money. Don't ignore this.

What To Do This Month

For individual developers:

1. Check your current usage. GitHub is launching a preview bill experience in early May. Look at your Billing Overview on github.com and see what your actual token consumption would have cost you the past few months.
2. Audit which models you use. Different models have wildly different per-token rates. If you're defaulting to the most expensive premium model for tasks GPT-5 mini could handle, that habit is about to cost real money.
3. Decide on annual vs monthly. If you're on annual, run the numbers before June 1.

For engineering teams:

1. Set up budgets. Admin-level budget controls let you cap spend at the enterprise, cost center, or user level. Use them. Without caps, one developer running parallel agent workflows can blow through your monthly credits in a week.
2. Pool credits across the org. GitHub now allows pooled included usage instead of per-seat isolation. This is genuinely useful — your light users effectively subsidize your heavy users without anyone changing behavior.
3. Educate your team on model selection. "Use the cheapest model that works for the task" is now a real engineering practice with a real budget impact.
4. Watch out for Copilot code review. It now consumes both AI Credits and GitHub Actions minutes. Two meters running at once.

The Bigger Picture

This isn't just a Copilot story. Every AI coding tool is heading the same direction — Cursor, Cody, Continue, Claude Code. Token-based pricing is becoming the default because flat-rate doesn't survive contact with agentic workloads.

The era of "$20/month gets you unlimited AI coding" is over. What's replacing it is more honest, but also more demanding: you need to know what your AI usage actually costs, and you need to manage it like any other infrastructure spend.

For teams that have been treating AI coding as a free productivity boost, that mental model needs to change before June 1.

The good news: the tools to manage this are getting better. Budget controls, usage dashboards, and pooled credits all help. The bad news: you actually have to use them.

---

Originally published on lenkastudio.com. We help teams ship modern web, mobile, and AI-powered products. If you're rethinking your AI dev tooling and budget for 2026, let's talk.