GitHub Tightens GitHub Copilot Individual Plans Amid Rising AI Compute Costs

GitHub is making significant changes to its Copilot Individual plans, including pausing new sign-ups, tightening usage limits, and adjusting model availability. These changes come as agentic AI workflows have fundamentally changed Copilot's compute demands, with long-running, parallelized sessions now regularly consuming far more resources than the original plan structure was built to support.

Why GitHub is Making These Changes

Agentic workflows have transformed how developers use GitHub Copilot. As Copilot's agentic capabilities have expanded rapidly, agents are doing more work, and more customers are hitting usage limits designed to maintain service reliability. Without further action, service quality degrades for everyone.

The core issue is that a handful of requests can now incur costs that exceed the plan price. These long-running, parallelized workflows can yield great value but have also challenged GitHub's infrastructure and pricing structure.

What's Changing

New Sign-Ups Paused

New sign-ups for GitHub Copilot Pro, Pro+, and Student plans are paused. This allows GitHub to serve existing customers more effectively while they work on a more sustainable solution.

Tightened Usage Limits

GitHub is tightening usage limits for individual plans. Pro+ plans offer more than 5X the limits of Pro. Users on the Pro plan who need higher limits can upgrade to Pro+.

Model Availability Changes

Opus models are no longer available in Pro plans. Opus 4.7 remains available in Pro+ plans. As previously announced in their changelog, Opus 4.5 and Opus 4.6 will be removed from Pro+.

Improved Transparency

Starting today, VS Code and Copilot CLI both display your available usage when you're approaching a limit. These changes are meant to help you avoid a surprise limit.

Usage limits in VS Code

Usage limits in Copilot CLI

How Usage Limits Work

GitHub Copilot has two usage limits today: session and weekly (7 day) limits. Both limits depend on two distinct factors—token consumption and the model's multiplier.

Session limits exist primarily to ensure that the service is not overloaded during periods of peak usage. They're set so most users shouldn't be impacted. Over time, these limits will be adjusted to balance reliability and demand. If you do encounter a session limit, you must wait until the usage window resets to resume using Copilot.

Weekly limits represent a cap on the total number of tokens a user can consume during the week. GitHub introduced weekly limits recently to control for parallelized, long-trajectory requests that often run for extended periods of time and result in prohibitively high costs. The weekly limits for each plan are also set so that most users will not be impacted.

If you hit a weekly limit and have premium requests remaining, you can continue to use Copilot with Auto model selection. Model choice will be reenabled when the weekly period resets. If you are a Pro user, you can upgrade to Pro+ to increase your weekly limits. Pro+ includes over 5X the limits of Pro.

Usage limits are separate from your premium request entitlements. Premium requests determine which models you can access and how many requests you can make. Usage limits, by contrast, are token-based guardrails that cap how many tokens you can consume within a given time window. You can have premium requests remaining and still hit a usage limit.

How to Avoid Hitting Limits

If you are approaching a limit, there are a few things you can do to help reduce the chances of hitting it:

• Use a model with a smaller multiplier for simpler tasks. The larger the multiplier, the faster you will hit the limit.
• Consider upgrading to Pro+ if you are on a Pro plan to raise your limit by over 5X.
• Use plan mode (VS Code, Copilot CLI) to improve task efficiency. Plan mode also improves task success.
• Reduce parallel workflows. Tools such as /fleet will result in higher token consumption and should be used sparingly if you are nearing your limits.

What If These Changes Don't Work for You?

If you hit unexpected limits or these changes just don't work for you, you can cancel your Pro or Pro+ subscription and you will not be charged for April usage. Please reach out to GitHub support between April 20 and May 20 for a refund.

The Bigger Picture

These changes reflect the broader challenge facing AI companies as agentic workflows become more sophisticated. The compute costs of running these advanced AI models have grown significantly, and the original pricing structures weren't designed for the current usage patterns.

GitHub acknowledges that these are their problems to solve. The actions they're taking today enable them to provide the best possible experience for existing users while they develop a more sustainable solution.

For developers currently using GitHub Copilot, the key takeaways are to monitor your usage through the new transparency features, consider whether you need to upgrade to Pro+ for higher limits, and be aware that model availability is changing. The pause on new sign-ups suggests GitHub is taking a step back to reassess their pricing and infrastructure strategy for individual users.

The company promises more sustainable solutions are in development, but for now, existing users will need to adapt to these new guardrails while GitHub works to balance the incredible value of agentic AI workflows with the economic realities of running them at scale.