Changes to GitHub Copilot Individual plans
Summary
GitHub is implementing changes to GitHub Copilot Individual plans, including pausing new sign-ups for Pro, Pro+, and Student plans and tightening usage limits. These adjustments are a response to the increased compute demands and resource consumption driven by agentic workflows and parallelized sessions.
Key Points
- New sign-ups for GitHub Copilot Pro, Pro+, and Student plans are currently paused to prioritize service for existing customers.
- Usage limits for individual plans are being tightened; Pro+ plans provide more than 5x the limits available in the Pro plan.
- Model availability is changing: Opus models are being removed from Pro plans, and while Opus 4.7 remains in Pro+, Opus 4.5 and 4.6 are being removed from Pro+.
- Real-time usage monitoring is now integrated into VS Code and Copilot CLI to notify users when they are approaching limits.
- Users can cancel Pro or Pro+ subscriptions and receive a prorated refund for the remaining subscription time by visiting Billing settings before May 20.
Technical Details
GitHub Copilot usage is governed by two distinct constraints: session limits and weekly (7-day) limits. Session limits are designed to prevent service degradation during peak usage periods, while weekly limits act as a token-based cap to manage the high costs associated with long-trajectory, parallelized requests. Both limits are calculated based on a combination of total token consumption and a model-specific multiplier; using models with higher multipliers will deplete usage quotas more rapidly.
To maintain service stability, developers can optimize their usage by selecting models with smaller multipliers for simpler tasks, utilizing "plan mode" in VS Code or Copilot CLI to improve task efficiency, and reducing the frequency of parallel workflows, such as the /fleet command. If a weekly limit is reached, users can continue to use Copilot via Auto model selection, but premium request entitlements will be restricted until the weekly period resets.
Impact / Why It Matters
Developers may encounter unexpected service interruptions or reduced model access if their agentic workflows exceed the new token-based thresholds. Users requiring high-throughput, parallelized coding tasks may need to upgrade to Pro+ to access significantly higher usage limits.