GitHub Copilot tightens limits for better service stability

GitHub Copilot’s evolving capabilities have reshaped how developers use AI-assisted coding, but skyrocketing demand now threatens service stability. To address this, GitHub is implementing stricter measures across Individual plans, pausing new sign-ups, and adjusting model availability. These changes prioritize existing users while preparing for a more sustainable future.

Why GitHub Copilot is adjusting its plans

The rapid adoption of agentic workflows has dramatically increased the computational demands on GitHub Copilot. Tasks that once ran for minutes now execute in parallel for hours, consuming token volumes far beyond the original plan structure. As Copilot’s agentic features expand, more users are triggering usage limits designed to protect service reliability. Without intervention, service quality would degrade for everyone.

GitHub acknowledges the frustration these changes may cause, emphasizing transparency in its approach. The company states these adjustments are essential to maintain a predictable experience for existing customers as it works toward a long-term solution.

Key changes affecting Individual plan users

GitHub’s latest updates introduce several significant modifications to Individual plans:

• New sign-ups paused: Registration for GitHub Copilot Pro, Pro+, and Student plans is temporarily suspended. This allows GitHub to focus on serving existing customers without added strain.
• Tighter usage limits: Pro+ plans now offer over five times the capacity of Pro plans. Users on Pro who require higher thresholds are encouraged to upgrade.
• Model access adjustments: Opus 4.7 remains available exclusively in Pro+ plans. Opus 4.5 and Opus 4.6 will be removed from Pro+ as previously announced.
• Clearer usage tracking: VS Code and Copilot CLI now display real-time usage data, helping users avoid surprise limits.

Affected users can cancel their Pro or Pro+ subscriptions and receive prorated refunds by May 20 through Billing settings.

How usage limits work under the new rules

GitHub Copilot enforces two primary limits: session-based and weekly (7-day) caps. Both depend on token consumption and model-specific multipliers.

• Session limits prevent service overload during peak demand. They are set conservatively so most users remain unaffected. Hitting a session limit requires waiting for the usage window to reset before resuming.
• Weekly limits cap total token consumption over seven days. Introduced recently, these guardrails target parallelized, long-running tasks that drive up costs. Limits are calibrated to minimize disruption for typical users.

Usage limits operate separately from premium request entitlements. While premium requests determine model access and request volume, usage limits cap token consumption within fixed timeframes. Users may still encounter usage limits even with premium requests remaining.

Upgrading to expand your capacity

Pro users facing usage constraints can upgrade to Pro+ for over fivefold increase in their weekly limits. This option benefits developers running complex, resource-intensive workflows.

Tips to avoid hitting usage limits

GitHub recommends several strategies to manage token consumption and prevent unexpected interruptions:

• Opt for models with smaller multipliers for simpler tasks to conserve tokens.
• Consider upgrading to Pro+ if Pro limits are too restrictive.
• Use plan mode in VS Code or Copilot CLI to optimize task efficiency and success rates.
• Minimize parallel workflows, especially with tools like /fleet, which accelerate token burn.

VS Code and Copilot CLI now show your remaining usage when nearing a limit, providing early warnings to adjust workflows accordingly.

The road ahead for GitHub Copilot

GitHub’s adjustments reflect a broader industry challenge: balancing rapid AI adoption with sustainable infrastructure. The company acknowledges that agent-driven workloads, while valuable, impose costs that often exceed plan pricing. These changes lay the groundwork for a more scalable solution while ensuring current users retain a reliable experience.

Looking ahead, GitHub plans to refine its pricing and infrastructure models to better align with evolving usage patterns. For now, existing users remain the priority as the platform adapts to the demands of the modern developer.