Quick Facts
- Category: Open Source
- Published: 2026-05-02 01:06:54
- Amazon Bedrock Guardrails Now Enforces AI Safety Policies Across All AWS Accounts at Scale
- How to Effectively Advocate Against Climate-Exacerbating Policies: A Step-by-Step Guide
- Valve Breaks Four-Year Silence with Major Update to Networking Library Used by Counter-Strike and Dota 2
- 5 Breakthroughs Unleashed by OpenAI’s GPT-5.5 on NVIDIA Infrastructure
- Mastering Direct Examination: Lessons from a High-Profile Courtroom Blunder
Overview: Protecting Service Reliability for Existing Users
GitHub has announced significant updates to its Copilot Individual plans, designed to safeguard the experience for current subscribers. The changes include pausing new sign-ups for select plans, tightening usage limits, and modifying model availability. While these adjustments may cause some disruption, they are necessary to maintain a stable and reliable service as Copilot’s capabilities evolve. This article breaks down what’s changing, why, and how it affects you.

Why These Changes Are Necessary
The rapid expansion of agentic workflows within Copilot has fundamentally changed its compute demands. Long-running, parallelized sessions now consume far more resources than the original plan structure was built to support. As Copilot’s agentic capabilities have grown—with agents performing increasingly complex tasks—more users are hitting usage limits that were originally designed to ensure service reliability. Without these updates, the quality of the service could degrade for everyone.
The Impact of Agentic Workflows
Agentic workflows allow Copilot to run multiple, extended tasks simultaneously. This shift from short, isolated queries to sustained, resource-intensive operations has strained the existing plan framework. GitHub has recognized that the old limits no longer suffice and that clearer communication about guardrails is essential.
Key Changes to Plans
Three major updates are being rolled out: paused sign-ups, tighter usage limits, and adjusted model availability. Each is aimed at balancing capacity and reliability.
Paused Sign-Ups for Individual Plans
New sign-ups for GitHub Copilot Pro, Pro+, and Student plans are temporarily paused. This pause allows GitHub to focus resources on serving existing customers more effectively, ensuring they continue to receive a predictable experience.
Tightened Usage Limits
Usage limits are being tightened for individual plans. Pro+ plans now offer more than five times the limits of Pro plans. Users on the Pro plan who need higher ceilings can upgrade to Pro+. To help you stay within your limits, GitHub has added real-time usage displays in VS Code and the Copilot CLI, making it easier to monitor consumption before hitting a cap.
Model Availability Adjustments
Certain Opus models have been removed from the Pro plan. Specifically, Opus 4.5 and Opus 4.6 are being phased out, while Opus 4.7 remains available exclusively in Pro+ plans. This change reflects the higher resource demands of these models and aligns with the broader effort to tier capabilities based on plan level.

Understanding Usage Limits in GitHub Copilot
Copilot now employs two types of usage limits: session limits and weekly limits. Both are influenced by token consumption and a model-specific multiplier.
Session Limits
Session limits exist primarily to prevent the service from being overloaded during peak usage periods. These limits are set high enough that most users should not be affected. If you do encounter a session limit, you must wait until the usage window resets before you can resume using Copilot. Over time, GitHub plans to adjust these limits to balance reliability and demand.
Weekly Limits
Weekly limits cap the total number of tokens a user can consume over a seven-day period. They were introduced to control costs associated with parallelized, long-trajectory requests that run for extended periods. Like session limits, weekly limits are set so that the majority of users will not be impacted. If you hit a weekly limit but still have premium requests remaining, you can continue—though the specifics depend on your plan.
Your Options and Next Steps
If these changes do not work for you, or if you encounter unexpected limits, you have the option to cancel your Pro or Pro+ subscription. GitHub is offering a refund for the remaining time on your current subscription if you cancel by May 20. To do so, visit your billing settings. For those who stay, the new limits and model availability are designed to ensure a more reliable and predictable Copilot experience moving forward.