GitHub Copilot June 2026 billing change: what the AI Credits switch means for your monthly bill
TL;DR: GitHub Copilot switched from flat Premium Request Units to token-based AI Credits on June 1, 2026. Plan prices are unchanged, but the billing math is entirely different — and if you use agent mode daily with frontier models, your effective cost can jump 10x to 50x. Light completions-and-chat users are probably fine; daily agentic users need to run the numbers before their first credit bill arrives.
| Copilot Pro | Copilot Pro+ | Copilot Max | |
|---|---|---|---|
| Monthly price | $10 | $39 | $100 |
| Credits included | $15 (base + flex) | $70 (base + flex) | $200 (base + flex) |
| Best for | Completions + light chat | Regular chat + code review | Daily agent mode, frontier models |
| The catch | 1,500 credits burns fast on o3 | Still no rollover on unused flex | $200/mo is steep unless you’re already near that on API costs |
Honest take: Stay on Pro ($10/mo) if your workflow is 90% inline completions. Move to Pro+ ($39/mo) if you run code review or switch models regularly. The new Max plan ($100/mo) only makes sense if you’re already spending that much across Cursor Pro and API credits — otherwise you’re buying insurance you’ll resent paying for.
What was the old system
Until May 31, 2026, GitHub Copilot charged for AI-powered chat, code review, and agent interactions using Premium Request Units (PRUs). Every premium interaction — a quick chat question or a 20-step agent session — cost one PRU, regardless of how much compute it actually consumed. Copilot Pro ($10/mo) came with 300 PRUs per month; additional requests cost $0.04 each.
That model had one useful property: predictability. You knew 300 requests was your monthly budget. Heavy users who burned through PRUs fell back to a lighter model rather than getting cut off entirely.
It also had a major flaw from GitHub’s perspective: a brief “what does this function do?” and a 150-turn refactoring agent session consumed the same one PRU. The economics broke badly once agent mode shipped.
What changed on June 1
The PRU system is now legacy. Starting June 1, 2026, every paid Copilot plan includes a monthly allotment of GitHub AI Credits, where 1 AI credit = $0.01, and usage is calculated against each model’s API token rates — input tokens, output tokens, and cached tokens all count.
What still costs nothing: Inline code completions and Next Edit Suggestions remain unlimited across all plans, credit balance irrelevant. If your Copilot workflow is mostly accepting tab completions, you will notice zero change.
What now burns credits: Copilot Chat, agent mode, code review, Copilot CLI, Copilot Spaces, and Copilot Spark. Each of these draws from your monthly credit balance at a rate that scales with the model you choose and how many tokens the exchange consumes.
The other material change: there is no more fallback model. Under the old system, exhausting your PRUs dropped you to a lower-cost baseline model so you could keep working. Under the new system, when your credits run out, you stop — unless your organization’s admin has configured a spending limit or budget top-up.
Plan-by-plan: the actual credit math
Here is the current structure, confirmed from the official GitHub Copilot plans page:
| Plan | Price | Base credits | Flex allotment | Total included |
|---|---|---|---|---|
| Free | $0/mo | Limited (Haiku 4.5 + GPT-5 mini only) | — | — |
| Pro | $10/mo | $10 (1,000 credits) | $5 (500 credits) | $15 (1,500 credits) |
| Pro+ | $39/mo | $39 (3,900 credits) | $31 (3,100 credits) | $70 (7,000 credits) |
| Max | $100/mo | $100 (10,000 credits) | $100 (10,000 credits) | $200 (20,000 credits) |
| Business | $19/user/mo | $19/user | — | — |
| Enterprise | $39/user/mo | $39/user | — | — |
A few things worth noting in that table:
The flex allotment is real money, not marketing. Pro includes $5 in flex credits on top of the $10 base. That is 1,500 credits total, not 1,000 — a meaningful 50% bump. Pro+ gets $70 total ($39 base + $31 flex), nearly double the base figure. GitHub is essentially pre-loading overage so you don’t immediately hit a hard wall.
Credits do not roll over. Unused base and flex credits expire at the end of each billing cycle. If you burn $4 of your $10 base in a slow month, the remaining $6 disappears. The old PRU model had the same expiry behavior, so this is not new, but it matters more now that credits are denominated in dollars.
The Max plan is new. It did not exist before. At $100/mo with $200 in total credits, it is explicitly designed for developers running sustained, high-volume agent workflows — teams where Copilot agent mode is replacing meaningful chunks of sprint work, not supplementing it.
Model pricing: the part that will surprise you
Under PRUs, model choice did not affect your monthly limit. Under AI Credits, it determines everything.
Community analyses of GitHub’s published API token rates show roughly these per-interaction costs at typical exchange lengths:
| Model | Estimated cost per simple chat turn | Estimated cost per agent session (multi-file) |
|---|---|---|
| GPT-5 mini / Haiku 4.5 | ~1 credit ($0.01) | ~5–15 credits ($0.05–$0.15) |
| GPT-4o | ~1 credit ($0.01) | ~10–25 credits ($0.10–$0.25) |
| Claude Sonnet 4.6 | ~4–5 credits ($0.04–$0.05) | ~60–100 credits ($0.60–$1.00) |
| OpenAI o1 | ~10 credits ($0.10) | ~50–100 credits ($0.50–$1.00) |
| OpenAI o3 | ~46 credits ($0.46) | ~200–400 credits ($2.00–$4.00) |
These are estimates derived from token rates and typical exchange sizes, not guaranteed per-request prices — actual cost varies by conversation length, file context passed, and model reasoning budget. But the order of magnitude differences are real.
On a Copilot Pro plan ($15 total credits), that means:
- GPT-4o chat only: roughly 1,500 quick exchanges, or 60–150 focused agent sessions → comfortable
- Claude Sonnet 4.6 agent sessions: roughly 15–25 sessions before credits run out → tight
- o3 agent sessions: roughly 3–7 sessions → gone in days for a power user
On Copilot Pro+ ($70 total credits), the math is considerably more forgiving for mid-range models, but o3 agentic work can still drain the allotment in under a week of heavy use.
Agent mode is where the billing change bites
The crux of the backlash — some developers on community forums and Visual Studio Magazine reporting 10x to 50x effective cost increases — is entirely concentrated in agent mode with frontier models.
A typical Copilot Chat exchange is cheap. You ask a question, Copilot responds, and you move on. Token consumption is bounded and predictable. But an agent session where Copilot iterates across a 5-file refactor, writes tests, catches lint errors, and revises its approach can consume thousands of tokens per step across dozens of steps. At Claude Sonnet 4.6 or o3 rates, a single productive agent session can cost $1–$4 in credits.
Under the old PRU model, that same session cost one PRU ($0.04). The billing difference is 25x to 100x on a per-session basis.
GitHub’s argument is that the PRU model was unsustainable for those workloads — it was effectively subsidizing heavy agent use at the expense of everyone else’s subscription. That argument is probably correct. It does not make the transition less jarring if you were one of the subsidized users.
5 ways to manage your credit budget
1. Pin a lighter model for routine chat. Switching from Claude Sonnet 4.6 to GPT-4o or GPT-5 mini for everyday questions (“what does this error mean?”, “write a docstring for this function”) reduces per-exchange cost by 80–95% with minimal quality drop for simple lookups. Reserve frontier models for tasks that actually need them.
2. Scope agent sessions tightly. Instead of handing Copilot agent mode a vague “refactor this module,” define a narrow task with a clear stopping point. Shorter context + fewer revision loops = fewer tokens consumed. A 200-token prompt that produces a focused result beats a 2,000-token conversation that wanders.
3. Use the billing dashboard before you’re surprised. GitHub’s billing interface now shows real-time credit consumption. Check it after your first week on the new system to understand your actual burn rate — do not wait until the renewal notice.
4. Set a spending limit. If you are on a team plan, your admin can configure per-user spending caps and alerts at threshold percentages. Individual users can configure overage spending (additional credits purchased at $0.01 each beyond the monthly allotment). Setting these up prevents bill shock without blocking your workflow entirely.
5. Triage what actually needs Copilot agent mode. The honest question is whether every agent invocation is worth $0.60–$4.00. Some tasks are — a reliable refactor across 10 files is worth $2 if it takes 3 minutes instead of 30. A lot of speculative “let’s see what Copilot does with this” exploration is better done with inline completions, which remain free.
When it makes sense to move to Cursor, Windsurf, or Claude Code instead
If you are a heavy agent-mode user hitting $50–$100+ per month on the new Copilot billing, you are in territory where alternatives start penciling out differently.
Cursor Pro ($20/mo) includes its agentic features in the flat rate. The tradeoff is you’re in Cursor’s IDE environment, not VS Code with your existing extensions. For developers who spend 40%+ of their day in agent mode, Cursor Pro is likely cheaper than Copilot Pro+ at current usage patterns.
Windsurf ($20/mo) and Claude Code ($20/mo) operate similarly — flat subscription rates that include meaningful agentic usage rather than metering every token. Claude Code’s token costs at the Pro tier are significant for very heavy users, but the structure is different from Copilot’s new model.
The case for staying on Copilot: If your team is already standardized on GitHub, the code review integration is tightly woven into your PR workflow, and you primarily use completions with occasional chat, Copilot Pro at $10/mo remains the most cost-efficient option on the market. The billing change only hurts if you were using agent mode heavily — and if you were using it heavily under PRUs, you were already getting a subsidized deal.
See the full platform comparison for a side-by-side breakdown of what each tool actually does in practice.
Frequently Asked Questions
Does the billing change affect code completions? No. Inline code completions and Next Edit Suggestions remain unlimited across all paid plans and do not consume AI Credits. The change only applies to Copilot Chat, agent mode, code review, CLI, Spaces, and Spark.
What happens when I run out of credits mid-month? Previously, exhausting Premium Request Units triggered a fallback to a lower-cost model. Under the new system, there is no fallback — you stop receiving AI-powered responses until the next billing cycle, or until you purchase additional credits at $0.01 per credit. Organizations can configure spending limits to prevent hard cutoffs.
Is the new Max plan ($100/mo) worth it? Only for developers running Copilot agent mode daily with frontier models like o3 or Claude Sonnet 4.6. At $200 in total monthly credits, Max provides roughly 200–300 substantive agent sessions at Claude Sonnet rates. If you are doing fewer than 50 agent sessions per month, Pro+ at $39/mo (with $70 in credits) is almost certainly sufficient.
Did the plan prices actually change? No. Pro is still $10/mo, Pro+ is still $39/mo, Business is $19/user/mo, Enterprise is $39/user/mo. What changed is what those dollars buy: the new billing structure gives Pro users $15 in credits (not just $10) and Pro+ users $70 in credits due to the flex allotment, which is technically more purchasing power than the old 300 PRU / $12 effective cap for Pro.
Should I switch off Copilot because of this? For most developers using Copilot primarily for completions and occasional chat, no. The billing change will not significantly affect your monthly experience. For daily agent-mode power users, the economics have genuinely shifted — running the numbers against Cursor or Claude Code’s flat rates is worth doing before your next renewal. The AI API Cost Calculator lets you compare Claude, GPT, and other model costs by monthly bill to make that comparison concrete.
Sources
- GitHub Copilot plans and pricing — Official
- GitHub Copilot is moving to usage-based billing — GitHub Blog
- GitHub Copilot individual plans: Introducing flex allotments and Max plan — GitHub Blog
- Copilot to Usage Billing — community discussion #192948
- Announcement & FAQ: Changes to GitHub Copilot Individual Plans — community discussion #192963
- Devs Sound Off on Usage-Based Copilot Pricing Change — Visual Studio Magazine
- GitHub Copilot legacy requests documentation — GitHub Docs
Last updated June 1, 2026. Pricing and plan features change frequently; verify current state at github.com/features/copilot/plans before purchasing.
Was this article helpful?
Thanks for the feedback — it helps improve future articles.