GitHub Halts New Copilot Sign-Ups Amid Surging Agentic Workloads, Tightens Limits
GitHub halts new Copilot sign-ups, tightens usage limits, and removes some Opus models on individual plans due to surging demand from agentic AI workflows. Existing users have until May 20 to cancel for a refund.
Breaking: GitHub Pauses New Copilot Individual Subscriptions
San Francisco, CA – GitHub announced today an immediate halt to new sign-ups for its Copilot Pro, Pro+, and Student plans, citing unprecedented compute demands from agentic workflows. The move aims to protect service reliability for existing customers, the company said in a statement.
“Agentic workflows have fundamentally reshaped Copilot’s resource consumption,” said a GitHub spokesperson. “Long-running, parallelized sessions now regularly consume far more than our plan structure was designed to support.”
What’s Changing: Usage Caps, Model Removal
In addition to freezing new enrollments, GitHub is tightening usage limits for all individual plans. The Pro+ tier now offers more than five times the limits of the Pro tier. Users on Pro who need higher caps can upgrade to Pro+.
Usage limits — both per-session and weekly — are now visible directly in VS Code and Copilot CLI to help users avoid hitting them. Session limits prevent overload during peak times, while weekly limits cap total token consumption to control costs from long-running agent requests.
Opus models have been downgraded: Opus 4.7 remains available only on Pro+, while Opus 4.5 and 4.6 will be removed entirely from Pro+. “We know these changes are disruptive,” the spokesperson added. “We want to be completely transparent about why we’re making them.”
Background: The Agentic Shift
GitHub Copilot launched in 2021 as a simple code completion tool. But with the rise of agentic AI — autonomous agents that plan, execute, and iterate on tasks — the service’s compute footprint has exploded. Long-running, multi-step requests now consume tokens at rates that the original plan architecture never anticipated.
“The original plan structure was built for single-turn, low-latency completions,” explained Tech analyst Sarah Chen of CloudScape Research. “Agentic workflows can run for minutes, iterating across files and tools. That’s a fundamentally different cost profile.”
GitHub has been gradually adding guardrails, including weekly token caps introduced earlier this year. The company says further action is needed to prevent service degradation for all users.
What This Means for Users
Existing subscribers will see immediate changes. If you’re on the Pro plan, you may hit session or weekly limits more quickly during intensive agentic sessions. The new in-IDE notifications aim to reduce surprise, but users who rely on heavy agentic workloads may need to upgrade to Pro+.
For those who find the new limits unacceptable, GitHub offers a full refund: any Pro or Pro+ subscriber can cancel before May 20 and receive a prorated refund for remaining subscription time. Instructions are available in the Billing settings.
“These changes are necessary to ensure a predictable experience for the majority of users,” the spokesperson emphasized. “We’ll continue to adjust limits as we balance reliability and demand.”
Impact on Students and Developers
- New student sign-ups are paused indefinitely; existing student accounts are unaffected.
- Pro+ users retain access to Opus 4.7, but the older Opus models (4.5, 4.6) are being phased out.
- Developers heavily using agentic coding assistants (e.g., multi-file refactoring, autonomous testing) should monitor token usage closely.
GitHub says most users will not be impacted under normal usage. The company intends to update limits over time as the platform evolves.