GitHub Copilot Individual Plans: 8 Critical Updates You Should Know

GitHub Copilot is evolving rapidly. As agentic workflows and AI-driven coding become more advanced, the service's compute demands have surged. To maintain a high-quality experience for existing subscribers, GitHub has implemented a series of changes to its Individual plans—including pausing new sign-ups, tightening usage limits, and adjusting model availability. These moves may feel disruptive, but they're designed to protect service reliability and ensure that active users continue to get the best possible performance. Below, we break down every key change, what it means for you, and how to navigate the new landscape.

1. New Sign-Ups for Pro, Pro+, and Student Plans Are Paused

GitHub has temporarily stopped accepting new subscriptions to Copilot Pro, Pro+, and Student plans. This pause is a proactive measure to prevent overloading the system and to reserve resources for current paying customers. If you were thinking about upgrading or joining, you'll need to wait until sign-ups reopen. Existing users remain unaffected—your service continues as before. GitHub hasn't announced a specific timeline for reopening, but the move signals a commitment to quality over rapid expansion. This pause also gives the engineering team breathing room to fine-tune infrastructure ahead of future demand spikes.

2. Usage Limits Are Tighter—Pro+ Now Offers 5x More

To keep the platform stable, GitHub has reduced default usage thresholds for individual plans. Pro+ subscribers now get more than five times the limits of Pro users. If you're on the Pro plan and consistently bump against caps, upgrading to Pro+ is the recommended path. A helpful new addition: usage limits are now displayed directly inside VS Code and the Copilot CLI, giving you real-time visibility so you can adjust your workflow before hitting a wall. This transparency aims to reduce frustration and help plan-heavy coding sessions more effectively.

3. Opus Models Disappear from Pro, Shift on Pro+

The Opus family of models is being reorganized. Pro plans no longer have access to any Opus model, starting with the immediate removal of earlier variants. For Pro+ users, Opus 4.7 remains available, but Opus 4.5 and Opus 4.6 will be phased out, as previously announced in the changelog. This consolidation simplifies the model lineup and aligns with the higher compute tiers that Pro+ offers. If you relied on an older Opus version for specialized tasks, you'll need to migrate to Opus 4.7 or explore other available models on your plan.

4. Why All This Is Happening: Agentic Workflows Demand More

The root cause behind these changes is the explosive growth of agentic workflows. Unlike simple autocomplete suggestions, agentic Copilot sessions run long, parallelized operations that consume far more tokens per request. As these capabilities expand rapidly, more customers are hitting the original plan limits designed for lighter usage. Without intervention, service quality would degrade for everyone. By pausing sign-ups, tightening caps, and rebalancing model access, GitHub aims to keep the experience snappy and reliable for its existing user base.

5. Understanding the Two Types of Usage Limits

GitHub Copilot enforces two distinct limits: session limits and weekly limits. Session limits protect against peak traffic spikes; they reset after a short period and are set high enough that most users never notice them. Weekly limits, introduced more recently, cap the total number of tokens you can consume over a rolling seven-day window. These are specifically designed to rein in the cost of long-running, multi-step agentic requests. Both limits factor in token consumption and a model multiplier—heavier models deplete your allowance faster. Checking your status in the editor helps you stay ahead.

6. What Happens When You Hit a Limit

If you encounter a session limit, you must wait until the usage window resets before you can send new requests. For weekly limits, hitting the cap means no more premium queries until the week rolls over—though you can still use basic Copilot features if allowed under your plan. To avoid surprises, GitHub now shows your remaining allowance in VS Code and the CLI. If these tighter restrictions don't fit your workflow, you have an option: cancel your Pro or Pro+ subscription before May 20 and receive a refund for the unused portion of your current billing period.

7. Pro vs. Pro+: Which Plan Fits Your Needs?

With the new limits, the distinction between Pro and Pro+ is clearer than ever. Pro is ideal for casual or moderate users who don't run intensive agentic sessions. Pro+, at a higher price point, unlocks more than five times the weekly token allowance and retains access to Opus 4.7. If your daily coding involves complex, multi-file refactors or deep reasoning tasks, Pro+ is likely a worthwhile investment. Evaluate your typical token consumption in a week—if you frequently hit the Pro cap, the upgrade will save you from frequent interruptions.

8. What's Next: Ongoing Adjustments and Transparency

GitHub acknowledges that these changes are significant and has promised to communicate future adjustments more transparently. Usage limits will be periodically reviewed and tweaked to balance reliability with demand. The company also plans to enhance in-editor notifications about limit status, so you never get caught off guard. For now, existing customers can continue with their current service, and GitHub stresses that most users should not be affected by the new thresholds. If you are affected, the refund window gives you a safety net while you assess whether the revised plans still meet your needs.

We hope this overview helps you navigate the shifting terrain of GitHub Copilot Individual plans. The core takeaway: pause new sign-ups, tighter limits, Opus model changes, and a clear upgrade path to Pro+ for heavy users. As always, your feedback shapes future iterations—so stay tuned and keep coding.