GitHub Copilot's Surprise Announcement: Sign-Ups Paused, Opus Evicted From Pro, Rate Limits Now Visible

GitHub's April 30 announcement reads like a product retraction dressed as a billing update. New sign-ups for Copilot Pro, Pro+, and Student are paused indefinitely. Opus-family models are gone from Copilot Pro entirely. Rate limits are now visible in VS Code and the CLI instead of hiding behind opaque counters. And the whole thing lands 30 days before GitHub flips the entire billing model to token-based AI Credits. Individually, each change is defensible. Collectively, they tell a different story: GitHub mispriced its own product, and now it's making customers pay for the miscalculation.

The sign-up pause is the most revealing signal. GitHub didn't say "we're improving." It said "we're stopping new people from giving us money." That's not a product decision — that's a capacity constraint dressed in PR language. The company is either running out of inference budget for frontier models or discovering that flat-rate subscribers who actually use the product aggressively were costing more than their $10 or $19 monthly fees covered. Either way, the message to potential new Copilot customers is: come back later, maybe.

Existing subscribers got the Opus news simultaneously. Opus 4.7 and its predecessors are no longer available on Copilot Pro — even though Opus 4.7 is technically the newest and most capable Claude model GitHub offers. Pro+ keeps Opus 4.7, but Opus 4.5 and Opus 4.6 are being removed from Pro+ as well, leaving only Opus 4.7 as the premium Claude option. GitHub's stated rationale is that "rate limits required to keep Opus sustainable on Pro would result in a worse overall experience than using a capable model without those limits." Read that again. The official position is that the best model in the tier is too expensive to offer at the tier's price point.

The math is worth doing. Opus 4.7 launched at a 7.5× premium request multiplier — meaning each Opus interaction consumed 7.5 "requests" against a subscriber's monthly limit. As of May 1, that multiplier jumped to 15×. A single long agentic session — the kind of multi-file refactor or complex debugging run that Copilot is increasingly marketed to handle — can easily consume $30-40 in API-equivalent costs at that rate, according to calculations in the community forum. That's not an edge case. That's the use case GitHub has been advertising.

The visibility change is the one unambiguous improvement. VS Code and Copilot CLI now show explicit usage progress instead of vague "requests remaining" counters. Developers can finally see the meter running before they hit the wall, rather than discovering the limit mid-session when Copilot stops responding. Given that June 1 switches the billing unit from requests to tokens, this is GitHub's way of teaching users to read the new meter before the old one disappears. Credit where it's due: legible usage data is long overdue, and power users have been asking for it since Copilot launched.

What's harder to credit is the refund window. Cancel before May 20 and you get a prorated refund. Cancel after, and you're locked in for another month. The May 20 cutoff is 10 days before the June 1 billing transition, which means anyone who waits to see the new credit system in action before deciding whether to stay will discover they've committed to another billing cycle. That's a tight window wrapped around a product that's about to change its fundamental pricing structure. It reads less like a grace period and more like a retention mechanism with a countdown.

For existing Copilot Pro subscribers who picked the plan specifically for Opus access, the options are narrowing. Upgrade to Pro+ (which keeps Opus 4.7 but at 15×), find an alternative IDE-integrated coding assistant, or accept that the model you built workflows around is no longer available at the price you were paying. The direct Anthropic API looks increasingly attractive by comparison: Opus 4.7 via API is rate-limited by your own budget, not by GitHub's multipliers, and the per-token pricing is transparent rather than wrapped in request-count math you have to reverse-engineer.

The June 1 AI Credits transition will add another layer of complexity. Pro subscribers get 1,000 credits per month; Pro+ gets 3,900. Code completions stay free and unlimited. Chat, CLI, agents, and Spaces consume the credit budget. Unused credits expire at the end of each billing period — no rollover, unlike AWS or Google Cloud credits that behave like real currency. For teams with variable Copilot usage, this is pure waste. Heavy month, light month, same subscription cost, and only one of those months actually uses the allocation.

GitHub will argue — correctly — that the old flat-rate request model was unsustainable for a product that's evolved from autocomplete into an agentic coding platform. Long autonomous sessions across large repositories genuinely cost more to serve than the $10 Pro subscription covered. The billing transition is a rational response to that reality. But rational and well-executed are different things. Changing multiple variables simultaneously — model availability, pricing structure, rate limits, access tiers — without a clean migration path is how you turn an economically sound decision into a trust problem.

The community thread is already drawing the right conclusions: Opus was the only reason some developers paid for Pro, the sign-up pause signals GitHub couldn't forecast its own demand correctly, and the May 20 refund deadline is too tight to make an informed choice about the new system. These aren't complaints from freeloaders. These are paying customers telling GitHub that the product contract they signed up for has been materially rewritten.

What happens next depends on whether GitHub treats May and June as a correction period or a consolidation period. If the billing preview tool — available in Copilot settings starting early May — shows users that the new system is more predictable and more fairly priced than the old one, the anger fades. If the preview shows that the same usage patterns cost significantly more under AI Credits, expect a wave of downgrades and cancellations in June. The preview is GitHub's chance to get ahead of that conversation. So far, it hasn't taken it.

Sources: GitHub Community Discussion #192963, GitHub Copilot Plans, Usage-based billing docs, GitHub Blog Changelog — Claude Opus 4.7