4713
views
✓ Answered

GitHub Halts New Copilot Pro Sign-Ups Amid Surging Compute Demands

Asked 2026-05-02 17:27:05 Category: Open Source

San Francisco, CA — GitHub has abruptly paused new sign-ups for its Copilot Pro, Pro+, and Student plans, citing unsustainable compute demands driven by agentic workflows. The company announced the immediate freeze on subscriptions, effective today, to protect service quality for existing users.

“Agentic workflows have fundamentally changed Copilot’s compute demands,” a GitHub spokesperson said. “Long-running, parallelized sessions now regularly consume far more resources than the original plan structure was built to support. Without immediate action, service quality degrades for everyone.”

Existing subscribers remain unaffected, but the pause will remain in place indefinitely while GitHub rebalances its infrastructure. The move comes weeks after the company introduced new usage limits and model tier restrictions.

Usage Limits Tightened

GitHub is also tightening usage limits for individual plans. Pro+ users now receive more than five times the limits of Pro subscribers. Users on the Pro plan who need higher capacity can upgrade to Pro+.

GitHub Halts New Copilot Pro Sign-Ups Amid Surging Compute Demands
Source: github.blog

“We’ve heard your frustrations about usage limits and model availability,” the spokesperson added. “These changes are necessary to deliver a predictable experience for our paying customers.” Usage limits are now displayed directly in VS Code and Copilot CLI so users can track consumption in real time.

GitHub outlined two types of limits: session limits, which prevent overload during peak usage by capping tokens per session, and weekly limits, which cap total token consumption over a rolling seven-day window. The weekly limit was introduced recently to rein in costs from extended, multi-step agentic requests.

“We designed these limits so most users won’t be affected,” the company noted. “But if you hit the weekly limit and still have premium requests remaining, you can continue using Copilot on the basic tier.”

Model Availability Shifts

Opus models are no longer available on Pro plans. Opus 4.7 remains accessible on Pro+, but Opus 4.5 and 4.6 will be removed from Pro+ as previously announced in the changelog. The company said the changes reflect the need to align model access with infrastructure costs.

“We know these changes are disruptive,” the spokesperson said. “If any plan changes don’t work for you, you can cancel your subscription before May 20 and receive a full refund for the remaining time.”

GitHub Halts New Copilot Pro Sign-Ups Amid Surging Compute Demands
Source: github.blog

Background

GitHub Copilot, launched in 2022, provides AI-powered code suggestions powered by OpenAI’s models. The Individual tier originally offered unlimited completions at a flat monthly fee, but the rapid uptake of agentic workflows—where Copilot runs long, autonomous coding sessions—has dramatically increased per-user resource consumption.

Prior to today, GitHub had already introduced token-based limits and model tiers. The current freeze marks the most aggressive step yet to control runaway costs. The company says it will reassess the sign-up pause based on infrastructure improvements.

What This Means

For existing Pro, Pro+, and Student subscribers: no immediate changes to your service, but you will see tighter session and weekly limits. If you hit the ceiling, you can either wait for a reset or upgrade to a plan with higher limits.

Prospective users hoping to join the individual paid plans are blocked for now. The free tier (Copilot for Individuals with limited requests) remains open to new sign-ups. GitHub has not announced a timeline for reopening paid subscriptions.

The model restriction means Pro users lose access to Opus models entirely; only Pro+ retains Opus 4.7. “We encourage users who need the most capable models to consider upgrading,” GitHub said, “but we understand not every budget can accommodate that.”

GitHub recommends all users check their usage in the VS Code extension or CLI to avoid hitting limits mid-session. The company promises to communicate future limit adjustments more transparently.