GitHub Copilot Individual Plans: Updated Policies for Enhanced Reliability

Overview of Plan Adjustments

GitHub is implementing several modifications to its GitHub Copilot Individual plans, including a pause on new subscriptions for Pro, Pro+, and Student tiers, tighter usage limits, and changes to model availability. These measures are designed to preserve service quality for existing users as agentic workflows significantly increase computational demands. While these updates may cause inconvenience, they are essential to ensure consistent performance for all current customers.

Why These Changes Are Necessary

The rise of agentic workflows has transformed Copilot's resource consumption. Long-running, parallelized sessions now consume far more compute than the original plan architecture anticipated. As Copilot's agentic capabilities advance, agents perform more complex tasks, and more users are reaching usage thresholds intended to maintain reliability. Without these adjustments, overall service quality would deteriorate, affecting everyone's experience.

Specific Changes to Plans

Pause on New Sign-Ups

New registrations for GitHub Copilot Pro, Pro+, and Student plans are temporarily halted. This pause allows GitHub to allocate resources more effectively to existing subscribers, ensuring a stable and responsive service.

Tighter Usage Limits

Usage limits are being tightened for individual plans. The Pro+ plan now offers more than five times the limits of the Pro plan, providing a clear upgrade path for users needing higher capacity. To help you stay within these boundaries, usage limits are now visible directly in VS Code and the Copilot CLI, reducing the chance of unexpected interruptions.

Model Availability Adjustments

Opus models are no longer available on the Pro plan; they remain exclusive to Pro+. Specifically, Opus 4.7 continues to be accessible in Pro+, while older versions Opus 4.5 and Opus 4.6 will be removed from Pro+ as previously announced in the changelog.

Understanding Usage Limits

GitHub Copilot employs two types of usage limits: session limits and weekly (7-day) limits. Both depend on token consumption and a model-specific multiplier.

• Session limits are designed to prevent service overload during peak times. Most users should not be affected under normal usage. If you hit a session limit, you must wait for the usage window to reset before continuing.
• Weekly limits cap the total tokens consumed over a seven-day period. They were introduced to control the high costs associated with parallelized, long-running requests. These limits are set so that the majority of users will not encounter them. If you reach a weekly limit but still have premium requests remaining, you can continue using Copilot.

For detailed information on how limits are calculated and reset, refer to the Usage Limits section below.

What This Means for You

If you are a current subscriber, your service should remain stable. However, if you experience unexpected limits or find these changes unsuitable, you have the option to cancel your Pro or Pro+ subscription and receive a prorated refund for the remaining time in your billing period. To do so, visit your Billing settings before May 20.

For those on the Pro plan who need higher limits, upgrading to Pro+ is straightforward. The enhanced limits and continued access to Opus 4.7 (in Pro+) ensure you have the resources for demanding workflows.

Looking Ahead

GitHub will continue to monitor usage patterns and adjust limits as needed to balance reliability and customer needs. The pause on new sign-ups is temporary, and updates will be communicated through official channels. We appreciate your understanding as we refine Copilot to support advanced agentic capabilities while maintaining a high-quality experience for all users.