GitHub Copilot just got a lot more complicated — and not in a good way.
If you tried to sign up for Copilot Pro recently and hit a wall, that's not a bug. GitHub quietly paused new sign-ups for Copilot Pro, Pro+, and Student plans starting in late April 2026. No end date announced. No workaround offered. Just a message and a door that won't open.
That alone would be worth covering. But they made two other changes at the same time: Opus-family models are gone from the Pro tier, and rate limits are now visible inside VS Code and the CLI. Three changes, one announcement, and most developers only noticed the first one.
Let me walk through all three.
Sign-Ups Paused: Who's Locked Out
New individual subscribers can't get into Copilot Pro, Pro+, or Student right now. The pause covers all three. Business and Enterprise plans are unaffected — if you're a company buying seats, you can still do that.
Existing subscribers aren't being removed. Your plan, your access, your billing — none of that changes. The freeze only applies to net-new individual sign-ups.
GitHub's official language described it as a temporary pause while they work through capacity and operational costs. "Temporary" doesn't mean anything without a timeline, though. As of today (May 3), there's been no update on when the door opens back up.
The practical impact falls into two groups. If you're already in, nothing changes day-to-day. If you were just about to sign up — or if you recommended Copilot to a colleague and they went to subscribe — they're going to bounce.
Opus Models Gone from Pro
The second change is the one that'll actually affect current Pro subscribers.
Opus-family models have been removed from the $10/month Pro tier entirely. If you built any workflows around Opus inside Copilot — think complex reasoning tasks, long-context analysis, multi-step coding chains — those workflows don't work the same way anymore. The model access just isn't there.
What's still available on Pro? Haiku 4.5, GPT-5, and GPT-5 mini. Those cover completions, basic chat, and agent mode. They're capable models, genuinely useful for most day-to-day coding. But they're not Opus. The ceiling is meaningfully lower.
Claude Opus 4.7 moved up to Pro+ only. That's the $39/month tier. So if Opus is important to your workflow, you've got two options: upgrade and pay four times as much, or find an alternative.
It's worth being direct about the economics here. Going from $10/month to $39/month is a 290% price jump for Opus access. Microsoft didn't announce that as a price increase — they announced it as a "model change" — but from a user's perspective, that's what it is.
The rationale is inference costs. Running large models at scale is genuinely expensive, and GitHub's operational costs have reportedly climbed significantly since early 2026. Restricting the heaviest models to the highest tier is a predictable response to that pressure. It's not user-friendly, but it's not surprising either.
Rate Limits Are Now Visible
This one's quieter but actually useful once you get past the initial weirdness.
GitHub has started surfacing rate limit information directly in VS Code and the Copilot CLI. When you're approaching a limit, or when you hit one, the tooling will now tell you — specifically, not cryptically. You'll see what you hit, where you are, and (in some cases) when it resets.
Previously this was opaque. You'd get degraded completions or a vague error and have to piece together what was happening. Now the information is in the interface.
The catch is that surfacing this information makes people realize how real the limits are. Users who never noticed a ceiling before are now watching the counter tick down. Some teams that thought they had "unlimited" completions are discovering their usage patterns bump against soft ceilings more than they expected.
In fairness, the limits haven't tightened — the visibility has just increased. But there's a psychological difference between a limit you don't see and a limit you watch approach. Expect more forum threads about this over the next few weeks as the reality sets in.
For developers who manage team workflows or pair-code with Copilot heavily, the visible limit data is actually actionable. You can see which kinds of sessions burn through premium requests fastest and adjust accordingly — batching your complex reasoning tasks or routing lighter completions through Haiku to preserve budget for the heavier lifts. That's not a silver lining exactly. But it's real information you didn't have before, and some teams will use it well.
What This Means If You're Already a Subscriber
Most Pro subscribers are probably fine. If your workflow relies primarily on code completions, inline suggestions, and occasional chat — the models available on Pro handle that well. Haiku 4.5 is fast and competent. GPT-5 is genuinely good at coding tasks.
Where you might feel the Opus removal is in the longer, more complex requests. Multi-file context, architectural reasoning, code review at scale — those tasks benefited from Opus in ways that the current Pro model lineup doesn't replicate.
Test your actual workflow before you panic. Open your recent Copilot sessions and look at what models you were actually invoking. If Opus doesn't appear in your history, the change probably doesn't affect you. If it appears frequently, that's your signal that you need to either upgrade to Pro+ or rethink where you're using it.
Pro+ subscribers have the least to worry about. Opus 4.7 is still there, limits are visible now, and the plan is otherwise unchanged. The price point hurts more when you see what Pro users are getting turned away from, but the product itself is stable.
What This Means If You Were About to Sign Up
This is the rough situation. The answer is: wait, or look at alternatives.
If you're willing to wait, there's no reliable timeline on when the sign-up pause lifts. GitHub hasn't communicated one. You can set a bookmark on GitHub's changelog page and check back periodically, but that's about it.
If you can't wait — or if you need Opus access that's not locked behind $39/month — there are real alternatives worth evaluating. We've done a full side-by-side on Cursor vs. GitHub Copilot that's worth reading if you're in this position. Cursor's pricing structure is different, the model access story is different, and for some workflows it's a better fit even when Copilot is fully available.
The sign-up pause also changes the calculus a bit for teams. Business and Enterprise plans aren't frozen — you can still get Copilot for your org through those tiers. The per-seat cost is higher ($19/seat for Business), but if you need more than one or two seats, the team-level plans might be the only real path to Copilot access right now.
The Broader Pattern
These three changes fit together, and it's worth taking a step back.
GitHub is tightening the individual tier. They're pausing new sign-ups, restricting the most expensive models to the highest plan, and making usage limits more visible. That's a set of changes that reduces liability on their end — fewer users consuming expensive inference at low price points — while pushing the product toward enterprise revenue.
The Free tier stays free. That's a conscious choice to keep the funnel open. The argument is that the free product demonstrates value, builds habit, and eventually converts into team or enterprise accounts. That's probably true. But the middle of the market — the individual developer who wants a serious tool without an enterprise budget — just got squeezed. The $10 Pro tier is still priced like an entry product; it no longer performs like one.
For a detailed breakdown of what each Copilot plan costs and what you actually get, the GitHub Copilot pricing guide has the full picture. The tier comparison table there is especially useful if you're trying to decide whether Pro+ is worth the jump from $10 to $39.
Quick Summary
| What Changed | Impact |
|---|---|
| Sign-ups paused (Pro, Pro+, Student) | No new individual subscribers until further notice |
| Opus models removed from Pro | Pro users lose access to Opus; Pro+ has Opus 4.7 |
| Rate limits now visible in VS Code + CLI | Transparent but psychological — limits haven't changed |
The existing subscriber situation is stable, even if the model changes are annoying for some. The rough experience is for anyone who was about to join and is now bouncing off a closed door.
If you're locked out, the alternatives comparison is the most useful thing you can read right now. If you're in and wondering about the Opus situation, your call logs will tell you whether this actually affects your workflow or just sounds like it should.
And if you're just trying to figure out what GitHub Copilot costs in 2026 and whether any of the tiers make sense for your situation — the pricing breakdown has you covered.