🕵️ SicherheitslückenWeb Application Firewall Rule Bypass in Jetpack WAF Runtime(17.09.2026 um 16:34 Uhr)
🕵️ SicherheitslückenCross-Site Request Forgery in WooCommerce Product and Term Ordering(17.09.2026 um 16:34 Uhr)
🕵️ SicherheitslückenUnescaped Output in Enable Media Replace Error View(17.09.2026 um 16:34 Uhr)
🕵️ SicherheitslückenStored Cross-Site Scripting in WooCommerce Order Notes REST API v4(17.09.2026 um 16:34 Uhr)
🕵️ SicherheitslückenUnescaped Attribute Output in Enable Media Replace Upsell View(17.09.2026 um 16:34 Uhr)
🕵️ SicherheitslückenWeb Application Firewall Rule Bypass in Jetpack WAF Runtime(17.09.2026 um 16:34 Uhr)
🕵️ SicherheitslückenCross-Site Request Forgery in WooCommerce Product and Term Ordering(17.09.2026 um 16:34 Uhr)
🕵️ SicherheitslückenUnescaped Output in Enable Media Replace Error View(17.09.2026 um 16:34 Uhr)
🕵️ SicherheitslückenStored Cross-Site Scripting in WooCommerce Order Notes REST API v4(17.09.2026 um 16:34 Uhr)
🕵️ SicherheitslückenUnescaped Attribute Output in Enable Media Replace Upsell View(17.09.2026 um 16:34 Uhr)
🔧 Programmierung 🕛 vor 4 Monaten 8 Min Lesezeit
0

GitHub Copilot May 2026 Changes: Sign-Ups Paused, Opus Removed, Rate Limits Visible

↗ Quelle (dev.to)
🗣️ Stimme:
📑 Inhaltsübersicht

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 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, has you covered.

Vollständiger Original-Artikel
Den kompletten Beitrag mit allen Details direkt auf dev.to lesen.
↗ Original-Artikel auf dev.to lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 0%
🟡 In Evaluierung 0%
🟢 Keine Auswirkung 0%
Spannende Innovation 0%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
1 Quelle
Microsoft Office Ohne Abonnement? Jetzt kostet es ein paar Hundert - Jablíčkář
1 Quelle
Windows Defender: Falsche Warnung täuscht Sicherheitslücke vor - ad-hoc-news.de
1 Quelle
DFN-CERT-2026-4930 FFmpeg: Mehrere Schwachstellen ermöglichen u. a. das Ausführen ...
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten GitHub Copilot May 2026 Changes: Sign-Ups Paused, Opus Removed, Rate Limits Visible

Thematisch verwandte Begriffe: GitHub, Copilot, 2026, Changes · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...