GitHub Pauses Copilot Signups, Tightens Usage Limits

GitHub announced on April 20, 2026 that it is pausing new signups for individual Copilot plans and tightening usage limits to protect service reliability for existing paying customers. The pause affects signups for Copilot Pro, Copilot Pro+, and Student plans; Copilot Free remains available. Model availability is changing: Opus models are no longer available on Copilot Pro; Opus 4.7 remains available on Pro+, and Opus 4.5 and Opus 4.6 will be removed from Pro+.

The company cites growth in agentic, long-running, parallelized sessions as the root cause of rising compute demand and recent incidents that degraded performance. Key operational changes include:

• •Pausing new sign-ups for Copilot Pro, Copilot Pro+, and Student plans to prioritize existing customers.
• •Tightening usage quotas; Pro+ plans will offer more than 5X the limits of Pro. Usage warnings will appear in VS Code and the Copilot CLI, and usage progress tracking is coming soon.
• •Removing lower-tier access to older Opus models; Opus 4.7 is retained on Pro+, while Opus 4.5 and Opus 4.6 will be removed from Pro+ over time.

Billing and refund mechanics are explicit: users who find limits unacceptable can cancel Pro or Pro+ and request a prorated refund through May 20, 2026 via Settings → Billing and licensing → Licensing → Manage subscription → Cancel and refund subscription. GitHub warns of temporary authorization holds for usage-based costs and clarifies premium request quotas renew on the first of the month.

This is a product-level throttling and resegmentation response to a classic infrastructure scaling problem: usage patterns evolved faster than quota and pricing models. The shift toward agentic workflows means sessions can consume long-lived compute and parallel inferencing, which is expensive and fragile for shared, flat-rate plans. The changes follow multiple incidents in March that impacted GitHub services and mirror industry moves toward metered usage and quota enforcement seen across developer AI tooling.

For developers, this alters capacity planning. Projects that previously relied on flat monthly plans may now hit hard limits or incur additional charges if they need premium requests beyond allotted quotas. The explicit UI integrations for usage warnings in VS Code and the Copilot CLI are pragmatic: surface limits early to avoid silent failures in developer workflows.

Monitor how GitHub implements usage progress tracking and quota enforcement thresholds in editors and CI. Watch pricing and quota signals from competitors and model providers; tokenized or metered models will pressure teams to instrument usage and selectively route heavy workloads to dedicated infrastructure or Pro+ level subscriptions.

This is a defensive operational move that will force developers to treat Copilot usage as a metered resource. Expect increased emphasis on instrumentation, quota-aware design in coding agents, and potential migration paths to team or enterprise plans for heavy agentic workloads.