Introduction
GitHub Copilot has recently implemented significant changes to its Individual plans to manage the soaring compute demands caused by agentic workflows. These updates include pausing new sign-ups, tightening usage limits, and adjusting model availability. If you're an existing subscriber, this guide will walk you through exactly what has changed, how to understand your new limits, and what actions you can take to ensure uninterrupted service. By following these steps, you'll be able to navigate the new landscape smoothly and make informed decisions about your plan.
What You Need
- An active GitHub Copilot Individual plan (Pro, Pro+, or Student)
- Access to VS Code or GitHub Copilot CLI (to view usage limits)
- Your GitHub account credentials
- A basic understanding of your typical Copilot usage patterns (e.g., how many requests you make per day)
- (Optional) An email address to receive refund notifications if you choose to cancel
Step-by-Step Guide
Step 1: Understand What Has Changed
First, familiarize yourself with the three main changes:
- New sign-ups are paused for Pro, Pro+, and Student plans. This does not affect existing subscribers.
- Usage limits are tightened. Pro+ now offers more than 5 times the limits of Pro. Weekly limits are now displayed in VS Code and Copilot CLI.
- Opus models are no longer available on Pro. Opus 4.7 remains on Pro+; Opus 4.5 and 4.6 will be removed from Pro+ as announced in the changelog.
These changes are necessary because agentic workflows—long-running, parallel sessions—consume far more resources than originally planned. Without these adjustments, service quality would degrade for everyone.
Step 2: Check Your Current Plan and Usage Limits
Login to your GitHub account and navigate to your Billing settings to see which plan you're on. Then open VS Code or the Copilot CLI to view your current usage. Look for the new session limit and weekly limit indicators. The session limit prevents overload during peak times, while the weekly limit caps total token consumption. Both limits depend on token consumption and the model’s multiplier—higher-tier plans have more generous caps.
If you haven't hit any limits yet, you are likely in the normal usage range. If you have been hitting limits, note how often and during which tasks.
Step 3: Evaluate Whether You Need to Upgrade
Based on your usage patterns, decide if your current plan still meets your needs. If you are on the Pro plan and frequently exceed the weekly or session limits, consider upgrading to Pro+, which offers over 5x the limits. If you rely on Opus models, upgrading to Pro+ is essential because Opus models are no longer available in Pro. However, note that Opus 4.5 and 4.6 will be removed from Pro+ soon, leaving only Opus 4.7.
If your usage is moderate and you rarely hit limits, staying on Pro may be perfectly fine. Use the visibility of limits in VS Code to help gauge your needs.
Step 4: Monitor Your Usage Regularly
Check the usage indicators in VS Code and Copilot CLI at least once a week. These tools now display both your current session usage and your weekly token consumption. Set a reminder to check after heavy coding sessions or when running parallel agentic tasks. If you see you're approaching a limit, you can throttle back or schedule heavy work for the next reset period.
Remember: session limits reset after a short window; weekly limits reset every 7 days. Plan your work accordingly to avoid unexpected interruptions.
Step 5: Adapt Your Workflow to the Model Changes
If you are a Pro user who previously used Opus models, you must switch to the models still available in your plan. The changelog indicated that Opus 4.7 remains in Pro+, but if you stay on Pro, you will need to use other models (e.g., GPT-4 or Claude alternatives). For Pro+ users, ensure you are comfortable with the models that will remain after Opus 4.5 and 4.6 are retired. Test your workflows on the available models early to avoid last-minute disruptions.
Step 6: Cancel Your Subscription If Necessary (Before May 20)
If the changes do not work for you—for example, if you can't upgrade and your productivity is severely impacted—you have the option to cancel your subscription. Visit your Billing settings and request cancellation. You will receive a refund for the remaining time on your current subscription, provided you cancel before May 20. This is a limited-time option, so act promptly.
Tips for a Smooth Transition
- Keep an eye on your usage early and often. The new limits are designed so most users won't be affected, but early detection of issues allows you to adjust before hitting a wall.
- Consider upgrading to Pro+ if you rely on agentic workflows. The 5x limit increase significantly reduces the chance of interruption during long parallel sessions.
- Test model changes immediately. If you use Opus models, try alternatives on your current plan as soon as possible to avoid workflow breaks.
- Understand the reset windows. Session limits reset quickly; weekly limits are a fixed 7-day window. Plan your heavy usage for early in the week.
- Use the visibility tools in VS Code and CLI. They are there to help you stay informed. Bookmark the usage check step.
- Don't delay decision to cancel. If you are unhappy, the refund offer is only valid until May 20. After that, you may lose the refund window.