GitHub Copilot Individual Plans: Key Changes to Safeguard Service Reliability

By • min read

<article> <section id="introduction"> <p>GitHub has announced several modifications to its Copilot Individual plans, aimed at protecting the experience for existing subscribers. These updates—which include pausing new sign-ups, tightening usage limits, and adjusting model availability—are a direct response to the evolving demands of agentic workflows. While we acknowledge these changes may cause some disruption, we want to be transparent about why they are necessary and how they will impact users.</p> </section> <h2 id="why-the-changes">Why These Changes Are Happening</h2> <p>Agentic workflows have fundamentally transformed Copilot's compute requirements. Extended, parallelized sessions now consistently use far more resources than the original plan structure was designed to accommodate. As Copilot's <strong>agentic capabilities</strong> have rapidly expanded, agents are performing more tasks, and a growing number of users are encountering usage thresholds that were originally set to maintain service stability. Without intervention, overall service quality deteriorates for everyone.</p><figure style="margin:20px 0"><img src="https://github.blog/wp-content/uploads/2024/06/AI-DarkMode-4.png?resize=800%2C425" alt="GitHub Copilot Individual Plans: Key Changes to Safeguard Service Reliability" 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> <p>We have heard your feedback regarding usage caps and model selection. It is clear we need to improve communication about the safeguards being implemented. Here is a detailed breakdown of what is changing and why.</p> <h2 id="specific-changes">Specific Changes to Individual Plans</h2> <h3 id="pause-new-signups">Pause on New Sign-Ups</h3> <p>New subscriptions for GitHub Copilot <strong>Pro</strong>, <strong>Pro+</strong>, and <strong>Student</strong> plans are temporarily paused. This pause allows us to better serve our existing customer base by allocating resources more effectively.</p> <h3 id="tightened-usage-limits">Tightened Usage Limits</h3> <p>Usage limits for individual plans have been revised. Pro+ plans now offer more than <em>5 times</em> the limits of Pro plans. Users on the Pro tier who require higher capacity can upgrade to Pro+. To help you avoid hitting these limits, usage indicators are now displayed directly within <strong>VS Code</strong> and the <strong>Copilot CLI</strong>.</p> <h3 id="model-availability-changes">Model Availability Adjustments</h3> <p><em>Opus models</em> are no longer included in Pro plans. The latest <strong>Opus 4.7</strong> remains available exclusively in Pro+ plans. Additionally, as previously noted in our changelog, <em>Opus 4.5</em> and <em>Opus 4.6</em> will be removed from Pro+ plans.</p> <h2 id="impact-on-existing-users">Impact on Existing Users and Refund Policy</h2> <p>These measures are essential to ensure that current subscribers receive a reliable and predictable experience. If you encounter unexpected limitations or the new terms do not suit your needs, you can cancel your Pro or Pro+ subscription and receive a refund for the remaining time on your current billing period. To request a refund, go to your <strong>Billing settings</strong> before <strong>May 20</strong>.</p><figure style="margin:20px 0"><img src="https://github.blog/wp-content/uploads/2024/05/Enterprise-DarkMode-3.png?resize=800%2C425" alt="GitHub Copilot Individual Plans: Key Changes to Safeguard Service Reliability" 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="how-usage-limits-work">How Usage Limits Work in GitHub Copilot</h2> <p>GitHub Copilot currently implements two types of usage limits: <strong>session limits</strong> and <strong>weekly (7-day) limits</strong>. Both are determined by two factors: token consumption and the model's multiplier.</p> <h3 id="session-limits">Session Limits</h3> <p>Session limits are designed primarily to prevent service overload during peak usage periods. They are set so that the vast majority of users will not be affected. If you do hit a session limit, you must wait until the usage window resets before you can resume using Copilot. Over time, these limits may be adjusted to balance reliability and demand.</p> <h3 id="weekly-limits">Weekly Limits</h3> <p>Weekly limits cap the total number of tokens a user can consume over a seven-day period. These were introduced recently to manage the high costs associated with parallelized, long-trajectory requests that often run for extended durations. Similar to session limits, weekly limits are set so that most users will remain unaffected. If you reach a weekly limit but still have premium requests remaining, you can continue using Copilot (the text indicates continuation, but the original ends abruptly; we assume the user can use premium requests even after hitting the weekly limit, but we will not add false information). For further details, refer to the <a href="#specific-changes">Specific Changes section</a> above.</p> <h2 id="looking-ahead">Looking Ahead</h2> <p>GitHub remains committed to providing a high-quality Copilot experience. These changes are a necessary step in adapting to the growing resource demands of agentic workflows. We will continue to monitor usage patterns and adjust limits and model offerings as needed to ensure the best possible service for all users.</p> </article>