Understanding GitHub Copilot's Latest Plan Updates: What You Need to Know

GitHub Copilot has announced several important changes to its Individual plans, including pausing new sign-ups, tightening usage limits, and adjusting model availability. These updates are designed to protect the experience for existing customers as agentic workflows—long-running, parallelized sessions—have significantly increased computational demands. Without these measures, service quality could degrade for everyone. Below, we answer common questions about what's changing and how it may affect you. <h2 id="why-pause-signups">Why is GitHub Copilot pausing new sign-ups for individual plans?</h2> New sign-ups for GitHub Copilot Pro, Pro+, and Student plans are temporarily paused. This move allows GitHub to focus on serving existing customers more effectively. The rapid growth of agentic capabilities—where Copilot agents run multiple, long-duration tasks simultaneously—has put unprecedented strain on resources. By halting new subscriptions, GitHub can allocate compute power to current users, ensuring a reliable and predictable experience. Existing customers won't be affected, and the pause will be lifted once the infrastructure is better equipped to handle demand. This decision reflects a commitment to quality over expansion, even though it may disappoint potential new users.<figure style="margin:20px 0"><img src="https://github.blog/wp-content/uploads/2024/06/AI-DarkMode-4.png?resize=800%2C425" alt="Understanding GitHub Copilot's Latest Plan Updates: What You Need to Know" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: github.blog</figcaption></figure> <h2 id="usage-limits-changes">How will usage limits change for Pro and Pro+ plans?</h2> Usage limits are being tightened to maintain service stability. Pro+ plans now offer more than 5 times the limits of Pro plans, making them the better choice for heavy users. Users on the Pro plan who need higher capacity can <a href="#upgrade-pro-plus">upgrade to Pro+</a>. To help you avoid hitting these limits, GitHub now displays usage indicators directly in VS Code and the Copilot CLI. There are two types of limits: session limits (prevent overload during peak times) and weekly (7-day) limits (cap total token consumption). Most users won't be impacted, but if you do hit a limit, you'll need to wait for the window to reset or consider upgrading your plan. <h2 id="model-changes">What model changes are being made to Copilot Individual plans?</h2> GitHub is adjusting model availability to align with resource costs. Opus models are no longer available on Pro plans. However, Opus 4.7 remains accessible on Pro+ plans. Additionally, as previously announced in the changelog, Opus 4.5 and Opus 4.6 will be removed from Pro+ as well. These changes reflect the higher computational demands of advanced models; by limiting them to higher-tier plans, GitHub can ensure that users who need premium capabilities can still access them while maintaining performance for everyone. If you rely on Opus models, you may need to upgrade to Pro+ or adjust your workflow to use alternative models available on your current plan. <h2 id="how-limits-work">How do session and weekly usage limits actually work?</h2> GitHub Copilot uses two distinct limits: session limits and weekly limits. Session limits are designed to prevent the service from being overwhelmed during peak usage. They are set so that most users won't notice them—only those running exceptionally high-volume or parallel requests may be affected. If you hit a session limit, you must wait until the usage window resets before using Copilot again. Weekly limits cap the total tokens consumed over a rolling 7-day period. Token consumption is calculated by multiplying the actual tokens used by a model multiplier (which varies by model). These limits were introduced to control costs from long-running, multi-step agentic tasks. Upgrading to Pro+ raises these caps significantly, giving you more breathing room.<figure style="margin:20px 0"><img src="https://github.blog/wp-content/uploads/2024/05/Enterprise-DarkMode-3.png?resize=800%2C425" alt="Understanding GitHub Copilot's Latest Plan Updates: What You Need to Know" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: github.blog</figcaption></figure> <h2 id="upgrade-pro-plus">Can I upgrade from Pro to Pro+ to get higher limits?</h2> Yes, absolutely. If you're on the Pro plan and find the new limits too restrictive, you can upgrade to Pro+ directly from your billing settings. Pro+ provides over 5 times the usage limits of Pro, making it suitable for users who frequently run long, parallel agentic workflows. It also retains access to Opus 4.7 (though older Opus versions are being removed). The upgrade is seamless and immediately applies the higher limits. If you're unsure whether you need it, monitor your usage indicators in VS Code or CLI—if you're consistently hitting limits, Pro+ is likely worth it. <h2 id="refund-policy">What if these changes don't work for me? Can I get a refund?</h2> If the new restrictions negatively impact your experience, GitHub offers a straightforward exit option. You can cancel your Pro or Pro+ subscription and receive a full refund for the time remaining on your current billing period. To do so, visit your Billing settings before May 20. This ensures that users who are dissatisfied are not locked into a plan that no longer suits their needs. Keep in mind that cancellation will stop access to Copilot, so consider whether an upgrade to Pro+ might resolve your issues first. GitHub emphasizes that these changes are necessary for long-term service reliability, but they also respect your choice to leave. <h2 id="why-necessary">Why are these changes necessary for service reliability?</h2> Agentic workflows—where Copilot runs multiple, long-lasting, parallel tasks—have dramatically increased compute requirements. The original plan structure wasn't designed for such intensive usage, leading to frequent limit hits and potential service degradation. By pausing new sign-ups, tightening limits, and rationalizing model availability, GitHub can allocate resources more efficiently to existing customers. These adjustments ensure that performance remains predictable and fast, even as demand grows. Without them, everyone would experience slower responses and more interruptions. GitHub plans to continue monitoring and adjusting these guardrails over time to balance reliability with user needs.