As of June 1, 2026, annual Copilot Pro and Pro+ subscribers staying on request-based billing find their included premium requests worth considerably less. GitHub’s updated multiplier docs1 list Claude Opus 4.6 and 4.7 at 27x, Sonnet 4.6 at 9x, GPT-5.3 Codex at 6x, and Gemini 3.1 Pro at 6x, effective the moment GitHub’s new AI Credits model took over. These subscribers chose annual billing specifically to avoid this kind of drift.
The Multiplier Table: What Annual Subscribers Actually Pay After June 1
GitHub’s docs1 publish the before-and-after figures for annual plans staying on request-based billing:
| Model | Previous multiplier | June 1 multiplier |
|---|---|---|
| Claude Opus 4.6 | 3x | 27x |
| Claude Opus 4.7 | 15x | 27x |
| Claude Sonnet 4.6 | 1x | 9x |
| GPT-5.3 Codex | 1x | 6x |
| Gemini 3.1 Pro | 1x | 6x |
Some third-party coverage places Opus 4.7’s prior rate at 7.5x; the docs show it was 15x. The 7.5x figure applies to GPT-5.5’s promotional rate.
Code review carries a separate multiplier of 13 under the same billing change: each Copilot pull-request review or IDE code review drains the monthly premium request quota by 13, independent of the model backing it.2
The arithmetic is blunt. At 27x, a model invocation that consumed one premium request in January now consumes 27. Sonnet moves from parity to 9x. A subscriber who structured their workflow around Sonnet being effectively included at parity now has nine months of assumptions invalidated by a docs update.
Why Annual Plans Became a Trap: No Rollover, No Grandfathering
The multiplier shift would sting on a month-to-month plan. On an annual plan it creates a structural problem: there is no clean exit that costs nothing.
GitHub’s billing docs2 confirm that unused premium requests reset on the 1st of each month at 00:00 UTC, with no carry-over under either the current or new billing system. Whatever is left on May 31 resets. The argument that subscribers could bank requests before the cutover does not hold.
Annual subscribers locked in what they understood to be a fixed rate. GitHub is not raising the per-seat annual price. What changed is the exchange rate between a premium request and a model invocation. The multiplier table is the price hike; it is priced in a unit most subscribers weren’t tracking when they paid.
The Three Exit Options GitHub Offers (And What Each Costs)
GitHub’s docs1 describe three paths for annual subscribers staying on request-based billing:
Stay on the annual plan with the new multipliers until the plan expires, then auto-downgrade to Copilot Free. No immediate out-of-pocket cost, but effective capacity drops June 1.
Cancel for a prorated refund. The cleanest exit for subscribers who find the new multipliers unworkable, but it terminates a plan purchased specifically for price stability.
Upgrade to a monthly paid plan with prorated credits for the remaining annual value. This moves the subscriber onto the AI Credits model and removes the multiplier problem, but requires mid-cycle billing surgery on a plan whose value proposition was not having to do that.
None of these amounts to “keep what you paid for.”
Community Reaction: From ‘Rug Pull’ to Cursor Migration
GitHub Community Discussion #1929483, the main announcement thread, shows 848 downvotes against 20 upvotes. The top comments don’t debate whether frontier models deserve a premium price. They name alternatives3: Cursor at $20/month flat, Windsurf at $15/month flat, Claude Code, Cline, and Roo Code. The discussion has since been closed and locked, with GitHub directing subscribers to a follow-up thread.
Discussion #1929634 uses sharper language. Annual subscribers describe the change as a “bait-and-switch” and a “rug pull,” specifically noting that annual billing was chosen to lock in a rate. The objection isn’t that Opus is expensive; it’s that the cost of invoking Opus was not part of the advertised annual commitment at the time of purchase.
That reading of the contract is coherent. Annual plans are sold on price certainty. A multiplier table that retroactively reclassifies which models count as effectively included is a change to the plan’s value, even if the per-seat headline price holds.
The billing change was not GitHub’s only move. New sign-ups for Pro, Pro+, and Student plans were paused, usage limits were tightened, and GitHub announced that Opus 4.5 and 4.6 would be removed from Pro+ entirely, leaving Opus 4.7 as the only Opus model on that tier.4 For annual Pro+ subscribers who built workflows around Opus 4.6, the 27x multiplier is a secondary concern: the model is being deprecated off the plan.
Competitive Math: Cursor, Windsurf, and Claude Code at Flat Rate
The migration arguments in the community threads treat pricing legibility as the decision criterion. Users cite3 Cursor at $20/month and Windsurf at $15/month as alternatives that don’t require tracking per-model request multipliers.
The comparison isn’t fully clean. Cursor and Windsurf have their own usage policies, and the community discussions acknowledge this without letting it override the legibility argument. What these platforms offer is a single number per month, not a request budget that must be mentally cross-multiplied by per-model rates before it means anything.
For teams running Opus in automated loops, the June 1 change is a cost increase of roughly an order of magnitude. At 27x1, a workflow consuming 10 premium requests a month now consumes 270.
The structural pattern is not unique to GitHub. Annual contracts produce a captive subscriber base. When underlying costs shift, multiplier tables let a vendor reprice effective service without touching headline fees. Annual subscribers who locked in for price certainty are learning that “price” was defined more narrowly than they assumed.
Frequently Asked Questions
Does the June 1 multiplier change affect monthly Copilot subscribers the same way?
Monthly subscribers already migrated to the AI Credits model earlier in 2026 and are not subject to the request-based multiplier table at all. The 27x/9x/6x multipliers apply exclusively to annual Pro and Pro+ subscribers who remain on the legacy request-based billing system. Monthly-plan pricing is denominated in credits, not multipliers.
What happens to annual subscribers who do nothing before their plan expires?
They auto-downgrade to Copilot Free at the end of their current billing cycle, losing access to premium models entirely. Copilot Free includes only the base models with a limited monthly request cap and no access to Opus, Sonnet 4.6, or GPT-5.3 Codex at any multiplier.
How does the prorated refund for cancellation actually work?
GitHub calculates the refund based on the remaining full months left in the annual term, subtracting any premium requests already consumed. Subscribers who cancel mid-cycle lose access immediately upon cancellation, there is no grace period to finish a project or export settings.
Are enterprise or team Copilot plans subject to these same multipliers?
The published multiplier table and the three exit options apply only to Individual annual Pro and Pro+ plans. Enterprise and team plans negotiate model access through volume licensing agreements and are billed under a separate structure that does not use the per-request multiplier mechanism described in the Individual-plan docs.
Could GitHub adjust these multiplier values again before the annual plans expire?
GitHub’s docs present the multiplier table as the values effective June 1 for the duration of the legacy annual term, but the documentation does not include a contractual guarantee that the values will remain fixed. The precedent of mid-cycle multiplier changes on annual plans is exactly what triggered the current backlash, so a second adjustment during the same term cannot be ruled out by anything in the published policy.
