GitHub Copilot Individual Plans: 5 Key Changes and What They Mean for You

GitHub has rolled out significant updates to its Copilot Individual plans aimed at preserving service quality for current subscribers. These adjustments—pausing new sign-ups, tightening usage limits, and modifying model access—stem from the soaring computational demands of agentic workflows. Here’s a breakdown of the five essential changes you need to know, along with practical guidance on navigating the new landscape.

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

To better serve existing customers, GitHub has temporarily halted registrations for Copilot Pro, Pro+, and Student plans. This pause allows the company to allocate resources more effectively, ensuring that current users experience consistent performance. If you were considering signing up, you’ll need to wait until GitHub reopens enrollment. Existing subscribers remain unaffected, and the pause does not impact Team or Enterprise plans.

2. Usage Limits Tightened Across the Board

GitHub has implemented stricter usage limits for individual plans to prevent service degradation. The Pro+ plan now offers more than five times the limits of the standard Pro plan, making it a viable upgrade for heavy users. To help you stay within these boundaries, usage limits are now displayed directly in VS Code and Copilot CLI—no more guessing. If you’re on Pro and consistently hit ceilings, consider moving to Pro+ for a smoother experience. For a deeper dive into how these limits work, see section 4.

3. Model Availability Adjusted: Opus Changes

GitHub is refining its model lineup within Copilot. Opus models have been removed from the Pro plan entirely. However, Opus 4.7 remains accessible to Pro+ subscribers. Additionally, as previously announced in the changelog, Opus 4.5 and Opus 4.6 will be phased out from Pro+ soon. These changes aim to balance computational costs while still providing advanced model capabilities for higher-tier users.

4. Understanding the Two Types of Usage Limits

GitHub Copilot employs two distinct usage limits: session limits and weekly limits. Session limits prevent overload during peak times by capping short-term usage—these reset automatically after a brief period. Weekly limits, on the other hand, cap total token consumption over seven days, specifically targeting long-running, parallelized requests that can drive up costs. Both thresholds are set so that most users won’t notice them. However, if you engage in intensive agentic workflows, tracking your consumption via the in-editor indicators is wise.

5. What to Do If You Hit Limits or Need to Cancel

If these changes disrupt your workflow or you encounter unexpected caps, GitHub offers a straightforward solution: cancel your Pro or Pro+ subscription before May 20 to receive a full refund for the remaining period. Visit your Billing settings to initiate the process. For those who stay, the new limits are designed to ensure a predictable, high-quality experience for the majority of users. GitHub promises to continue monitoring and adjusting these thresholds as needed.

In summary, these five updates reflect GitHub’s commitment to maintaining reliability amid growing compute demands. While the changes may require some adjustment—especially if you relied on Opus models or unlimited usage—they also bring clearer visibility into your consumption and a clear upgrade path. Whether you upgrade to Pro+ or simply monitor your usage more closely, staying informed will help you make the most of your Copilot subscription.