GitHub Copilot has introduced several important updates to its Individual plans, designed to safeguard the experience for existing users. The changes include pausing new sign-ups, enforcing stricter usage quotas, and refining model selections. These adjustments stem from the rapid evolution of agentic workflows, which have placed unprecedented demand on computational resources. Here’s a clear breakdown of what’s happening and how it affects your use of Copilot.
Why These Changes Are Underway
Agentic workflows—long-running, parallelized sessions where Copilot acts more autonomously—have fundamentally shifted the compute landscape. These workflows now regularly consume far more resources than the original plan structure was built to accommodate. As Copilot’s agentic capabilities have expanded, agents are doing more work, and more customers are hitting limits that were originally designed to maintain service reliability. Without these changes, the quality of the service would degrade for everyone. We’ve also heard your frustrations about unclear limits and model choices, and these updates aim to bring more clarity and predictability.
Paused New Sign-Ups
New sign-ups for GitHub Copilot Pro, Pro+, and Student plans are currently paused. This pause allows us to focus on delivering a stable and reliable experience for existing customers. If you’re already subscribed, your service continues uninterrupted. If you were considering joining, we appreciate your patience as we work to strengthen the platform.
Tighter Usage Limits
We are tightening usage limits for Individual plans to better align with current resource demands. The Pro+ plan now offers more than five times the limits of the Pro plan, making it a suitable upgrade for heavy users. To help you stay within these bounds, usage limits are now displayed directly in VS Code and Copilot CLI—so you can see where you stand and avoid surprises. If you’re on Pro and need higher limits, upgrading to Pro+ is the recommended path.
Model Availability Adjustments
Opus models are no longer available in Pro plans. The latest Opus 4.7 model remains accessible in Pro+ plans. Additionally, as previously announced in our changelog, Opus 4.5 and Opus 4.6 will be removed from Pro+. This consolidation helps us maintain high-quality service for the models that offer the best performance.
Understanding Usage Limits in GitHub Copilot
GitHub Copilot employs two types of usage limits: session limits and weekly limits. Both are calculated based on two factors—token consumption and the model’s multiplier.
Session Limits
Session limits exist primarily to prevent the service from becoming overloaded during peak usage. They are set so that the majority of users should not be affected. If you do encounter a session limit, you’ll need to wait until the usage window resets before you can resume using Copilot. We’ll continue to adjust these limits over time to balance reliability and demand.
Weekly Limits
Weekly limits represent a cap on the total number of tokens a user can consume over a rolling seven-day period. These were introduced to control the cost and impact of long-running, parallel requests that can dramatically increase compute usage. Like session limits, weekly limits are set so most users will not be impacted. If you hit a weekly limit but still have premium requests remaining, you can continue using Copilot—subject to the remaining allocation.
What to Do If You’re Affected
If these changes result in unexpected limits or if the new structure simply doesn’t work for your workflow, you have options. You can cancel your Pro or Pro+ subscription and receive a refund for the time remaining on your current subscription. To do so, visit your Billing settings before May 20. We are committed to ensuring that existing customers have a predictable and satisfying experience, and these measures—though disruptive—are necessary to maintain that promise.