GitHub Pauses Copilot Individual Sign-ups, Tightens Limits
GitHub is pausing new sign-ups for Copilot Individual tiers and tightening usage caps to protect service reliability. New sign-ups for Pro, Pro+, and Student plans are paused immediately. Usage limits have been lowered for individual plans, with Pro+ retaining more than 5X the capacity of Pro; limits will be visible inside VS Code and the Copilot CLI. The Opus model family is being reshuffled: Opus 4.7 remains in Pro+, while Opus 4.5 and Opus 4.6 will be removed. GitHub cited four incidents in March that caused degraded performance and pointed to increased compute from agentic, long-running, parallelized sessions as the driver. Affected subscribers can cancel for a prorated April refund if they contact support between April 20 and May 20. GitHub also updated its status and Transparency Center data to improve visibility into platform health.
What happened
GitHub is changing Copilot Individual plans to stabilize service quality, pausing new sign-ups and tightening usage limits for existing individual tiers. The company paused sign-ups for Pro, Pro+, and Student plans, tightened per-user limits, and adjusted model availability so Opus variants are restricted to higher tiers. GitHub said there were four incidents in March that degraded performance, and that agentic, long-running, parallelized sessions now consume far more compute than the original plan structure supported.
Technical details
The immediate product changes are:
- •Paused new sign-ups for Pro, Pro+, and Student tiers.
- •Tightened usage limits for individual plans, with Pro+ offering more than 5X the limits of Pro. Limits are now surfaced in VS Code and the Copilot CLI.
- •Model availability adjustments: Opus 4.7 remains available in Pro+, while Opus 4.5 and Opus 4.6 will be removed from Pro+ and Opus models are no longer available in Pro.
GitHub attributes the changes to a shift in workload patterns: agentic workflows spawn long-running, parallel sessions that amplify compute and concurrency requirements. The company is also updating the status page and its Transparency Center with full 2025 data to give developers more visibility into reliability metrics.
Context and significance
This is a product-level rate limiting and tiering response to operational stress rather than a technical research advance. It signals that mainstream code-assistants are evolving from short-turn completions to agentic, multi-step workflows that have cloud-native resource and quota consequences. For practitioners, the move highlights the need to monitor runtime patterns, prefer higher tiers for parallelized workloads, and expect stricter quota governance from hosted AI coding services.
What to watch
Monitor changes to billed usage and the visibility of limits inside VS Code and Copilot CLI, and watch whether GitHub expands compute capacity or rearchitects agent execution to reduce per-session resource usage. Also track customer support volume during the April 20 to May 20 refund window.
Scoring Rationale
This is a notable product change with operational impact for many developers using Copilot. It affects access, billing, and workflows but does not alter the underlying AI research or the broader market structure. The change is time-sensitive for subscribers and signals infrastructure stress from agentic usage patterns.
Practice interview problems based on real data
1,500+ SQL & Python problems across 15 industry datasets — the exact type of data you work with.
Try 250 free problemsStep-by-step roadmaps from zero to job-ready — curated courses, salary data, and the exact learning order that gets you hired.
