GitHub Pauses Copilot Sign-Ups and Moves Every Plan to Token-Metered Billing as Agentic Workloads Outrun the Subscription Model

Overview

GitHub spent eight days in late April rewriting the economics of the most widely deployed AI coding assistant on the market. On April 20 the company paused new sign-ups for Copilot Pro, Pro+, and Student plans, tightened session and weekly usage limits, and removed Anthropic’s Opus models from the Pro tier. A week later, on April 27, it announced that every Copilot plan will move to usage-based billing on June 1, replacing the existing premium-request system with a token-metered “AI Credits” currency. The two announcements, taken together, mark the most significant restructuring of Copilot’s commercial terms since the product launched.

What Changed on April 20

In a post authored by Joe Binder, GitHub’s VP of product, the company said it was pausing new sign-ups for Copilot Pro, Pro+, and Student plans “to serve existing customers more effectively.” Binder attributed the move to a fundamental shift in how the product is being used: “Agentic workflows have fundamentally changed Copilot’s compute demands. Long-running, parallelized sessions now regularly consume far more resources than the original plan structure was built to support.”

GitHub introduced two new caps on individual plans: session limits intended to prevent service overload during peak usage, and weekly seven-day limits that cap total token consumption. Pro+ plans now offer more than five times the limits of the standard Pro tier, with notifications surfacing in VS Code and the Copilot CLI when users hit 75 percent of their allowance.

The model lineup was also reshuffled. According to The Register’s reporting on the suspension, Anthropic’s Opus 4.5 and Opus 4.6 were removed from Pro+ subscriptions, while the newly released Opus 4.7 became available to Pro+, Teams, and Enterprise customers at a 7.5x premium multiplier through April 30. Opus models were removed entirely from the cheaper Pro plan. The Register noted that Opus 4.7 “costs 20-40% more per token than predecessors,” and that nearly all users commenting in GitHub’s community forum opposed the changes.

GitHub offered existing Pro and Pro+ subscribers a refund window through May 20 for users who wanted to cancel rather than accept the new terms.

The June 1 Transition to AI Credits

The deeper structural change arrived on April 27, when GitHub said all Copilot plans would migrate to usage-based billing on June 1. The current Premium Request Units (PRUs) will be replaced with GitHub AI Credits, calculated from token consumption — input, output, and cached tokens — at published API rates for each model. One AI Credit equals $0.01 USD.

Under the new structure, each plan’s monthly subscription includes a credit allowance equal to its dollar price: Copilot Pro at $10 per month bundles $10 in AI Credits, Pro+ at $39 includes $39, Business at $19 per user per month includes $19, and Enterprise at $39 per user per month includes $39. Existing Business and Enterprise subscribers receive promotional top-ups through August.

GitHub framed the change as a response to a widening gap between subscription revenue and inference costs. Chief product officer Mario Rodriguez told The Register that “today, a quick chat question and a multi-hour autonomous coding session can cost the user the same amount,” arguing that the request-based model is no longer sustainable as agentic sessions consume orders of magnitude more compute than traditional chat or completion calls.

Code completions and Next Edit Suggestions — the original Copilot features — remain unlimited on paid plans even after a user exhausts the monthly credit allowance, GitHub confirmed.

The Opus 4.7 Multiplier

The single most striking number in the transition is the multiplier shift for premium models. According to The Register, Anthropic’s Opus 4.7 will jump from a 7.5x premium multiplier to 27x under the new credit system, while OpenAI’s GPT-5.4 will move from 1x to 6x. Because credits track token consumption directly, a long agentic run on Opus 4.7 will draw down a developer’s monthly allowance at a rate roughly 3.6 times faster than today’s premium-request math implied.

GitHub said it would launch a preview billing tool in early May to let users and administrators model their projected June bills before the cutover. Annual subscribers retain their PRU pricing until their term expires, and organizations gain pooled credit usage with budget controls at the enterprise, cost center, and user levels.

Developer Reaction

The announcements landed badly with much of Copilot’s existing user base. The Register characterized the response on GitHub’s own community forum as nearly uniformly negative, with developers questioning whether base subscription prices that stayed flat while limits tightened and credit allowances metered amounted to a stealth price increase. The framing that has dominated discussion threads — that paying customers “will get less, but pay the same price” — captures the central complaint: the headline subscription cost is unchanged, but the volume of work each plan can sustain has shrunk.

The shift also intensifies competitive pressure on Copilot’s individual tiers. AI-first editors built on the same underlying foundation models — including Cursor, which The Machine Herald has covered following its agent-centric Cursor 3 release — already compete on agentic workflows where Copilot’s new credit math is most punishing. Developers running long-horizon agent sessions are now incentivized to comparison-shop on token economics rather than seat licenses.

What We Don’t Know

GitHub has not disclosed how many Copilot Pro and Pro+ subscribers are affected by the sign-up pause, nor whether the suspension of new accounts is temporary or open-ended. The company has also not specified when, or whether, the model rotation will stabilize: Opus 4.5 and 4.6 were removed from Pro+ on April 20, and the new credit-based pricing for Opus 4.7 takes effect with the June 1 transition, leaving the intervening weeks governed by the legacy multiplier. Whether the preview billing tool launching in early May will be available to individual users or limited to organization administrators remains unclear from GitHub’s announcements.

The broader question — whether usage-based billing stabilizes Copilot’s unit economics or simply transfers cost volatility from GitHub onto its customers — will not be answerable until the first full billing cycle closes in early July.