GitHub Copilot Moves to Usage-Based Billing June 1. Opus Costs 27x Base Rate.

GitHub quietly updated its Copilot pricing multiplier table, and the numbers are jarring. Starting June 1, 2026, every Copilot interaction gets priced in "AI Credits" with per-model multipliers: Claude Opus at 27x the base rate, Claude Sonnet at 9x, and base completions at 1x. Opus models are gone from Pro plans entirely, locked behind Pro+ only. If you're on an annual subscription, the new multipliers hit immediately at switchover. No grace period. (Source)

Then, two days later, a second billing shock: GitHub announced that Copilot code review will also start consuming GitHub Actions minutes on the same June 1 date. The agentic review architecture runs on GitHub-hosted runners, so private repo reviews now draw from your Actions minute entitlements on top of AI Credits. Two billing changes, same date, compounding costs.

This isn't a minor pricing tweak. It's a structural shift in how developers will choose models. The flat-rate era trained us to always pick the best model available. Why use Sonnet when Opus is "free"? That behavior is now expensive. A developer who casually uses Opus for routine completions, code review, and refactoring will burn through credits at 27x the rate of someone who routes intelligently.

I've been watching this pattern across every major AI coding platform. Cursor moved to compute credits. Windsurf has premium request pools. Coatue and Ramp data from last week shows 74% of AI labs already use consumption-based pricing, while 96% of traditional SaaS companies remain on seat models. GitHub is catching up to what AI-native companies figured out months ago.

Here's what builders should do right now. First, audit your Copilot usage before June 1. Figure out which interactions actually benefit from Opus-tier reasoning versus which ones are fine with base completions. Second, implement model routing in your workflow. Use cheap models for autocomplete and boilerplate, reserve expensive models for complex reasoning and architecture decisions. Third, budget for it. If you're running a team of 10 developers and everyone defaults to Opus, your Copilot bill could jump 10-20x overnight. The era of "all you can eat" AI coding assistance is over.