GitHub Copilot Overhauls Individual Plans: New Sign-Ups Halted, Usage Caps Tightened, and Model Access Revised

Introduction

GitHub is rolling out major adjustments to its Copilot Individual plans, including pausing new subscriptions, enforcing stricter usage limits, and modifying which AI models are available. While these changes may cause some disruption, the company emphasizes they are necessary to maintain service quality for existing users in the face of surging demand from agentic workflows.

Why These Changes Are Happening

The core reason behind the overhaul is the dramatic shift in how Copilot is used. Agentic workflows—long-running, parallelized sessions—now consume far more computational resources than the original plan structure was designed to handle. As Copilot’s agentic capabilities have expanded, agents are performing more tasks, and more customers are hitting usage limits that were originally put in place to ensure system reliability. Without these adjustments, GitHub warns that service quality would degrade for everyone.

What Is Changing?

New Sign-Ups Paused

GitHub has temporarily stopped accepting new sign-ups for Copilot Pro, Pro+, and Student plans. By freezing new enrollments, the company aims to allocate resources more effectively to existing subscribers, ensuring they continue to receive a reliable experience.

Usage Limits Tightened

Both session and weekly usage limits have been revised. The Pro+ plan now offers more than five times the limits of the standard Pro plan, giving power users a clear upgrade path. To help users stay within their quotas, GitHub has added real-time usage displays in VS Code and the Copilot CLI, making it easier to monitor consumption and avoid interruptions.

Model Availability Changes

Opus models are no longer available on the Pro plan. Opus 4.7 remains accessible exclusively on Pro+. Additionally, as previously announced in the GitHub changelog, Opus 4.5 and 4.6 will be removed from Pro+ in the near future. These changes streamline the model lineup and align compute costs with plan tiers.

How Usage Limits Work in GitHub Copilot

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

Session limits are designed to prevent the service from being overwhelmed during peak usage periods. They are set so that the majority of users will not be affected. If you hit a session limit, you must wait until the usage window resets before continuing to use Copilot.

Weekly limits cap the total number of tokens a user can consume over a rolling seven-day period. This limit was introduced to control the costs of parallelized, long-trajectory requests that run for extended periods. For most users, the weekly limit will not be a constraint; however, if you exhaust your weekly allowance and still have premium requests remaining, you can continue to use the service—though you may be subject to additional restrictions or reduced performance.

What to Do If These Changes Affect You

If you encounter unexpected limits or find the new plan structure unsuitable, GitHub offers a straightforward remedy. You can cancel your Pro or Pro+ subscription and receive a full refund for the remaining time on your current billing period. To do so, visit your Billing settings before May 20. This grace period ensures that users who are dissatisfied have an easy exit without financial penalty.

Looking Ahead

GitHub acknowledges that these changes are disruptive, but the company believes they are essential for sustaining a high-quality experience as Copilot evolves. Over time, usage limits will be adjusted to balance reliability with demand. The company also promises to improve communication about the guardrails it is adding, addressing recent frustrations around transparency.

For now, existing customers can continue using Copilot with the assurance that GitHub is prioritizing their service stability. Those who need higher limits have a clear upgrade path to Pro+, while those who find the new restrictions too limiting can choose to leave with a refund. The pause on new sign-ups will remain in effect until GitHub is confident it can serve its current user base without compromise.