GitHub Copilot Drops Flat Subscription Pricing for Token-Based Billing, Triggering Developer Backlash

GitHub Copilot's billing model changed on Monday. As of June 1, every Copilot plan now runs on a currency called GitHub AI Credits, which drain as users work, priced according to the tokens each session burns across inputs, outputs, and cached context. The old flat-rate premium request unit system is gone.

The architecture decision driving the switch is straightforward: Copilot is no longer a text-autocomplete widget. According to the GitHub Blog post authored by GitHub Chief Product Officer Mario Rodriguez, the product "now powers far more complex, agentic workflows that consume far more compute." A quick chat prompt and a multi-hour autonomous coding session that reads and rewrites files across an entire repository are not the same operation, but under the old model both were counted as equivalent premium requests. GitHub says that asymmetry made the prior pricing model unsustainable.

Base subscription prices are not changing on paper. Copilot Pro stays at $10 per month, Pro+ at $39, Business at $19 per user, and Enterprise at $39 per user. What changed is what those numbers actually buy. Each plan now comes with a monthly credit allotment equal in dollar value to the subscription price, and once that allotment runs out, premium features stop until the next billing cycle or the user buys more credits. The prior model included a fallback to cheaper models when a user hit their limit. That fallback is gone.

The developer reaction has been immediate and loud. According to reporting by The Register, users on GitHub's own community forums described burning through a significant fraction of their monthly Pro+ allotment in two hours of ordinary work. One developer told the forum they had used roughly 8 percent of their 7,000-unit monthly allocation in that window, projecting depletion in under two days. Another reported a single project change cost more than $6. Developers on Reddit and X posted projections ranging from $29 to $750 per month and from $50 to $3,000, according to TechCrunch, which covered the surge in complaints before the billing change went live.

The complaint is not only about cost. It is about predictability. As one developer wrote in GitHub's community discussion, reviewed by this reporter, the switch is "a staggering shift from a 'predictable subscription' to a 'stressful meter-based' service." Copilot code review adds a second dimension: it now runs on an agentic architecture built on GitHub Actions, and each review pull request also consumes Actions minutes at standard per-minute rates, layering a second variable cost on top of the credit system.

GitHub has offered some cushion. Business and Enterprise customers get promotional extra credits for June, July, and August. The company is also introducing pooled usage for organizations, so unused credits from lighter users can offset heavier ones rather than going to waste at the end of a billing cycle. Admins can set budget caps at the enterprise, cost-center, and user levels.

The deeper issue here is not specific to GitHub. Agentic coding tools are fundamentally different from the autocomplete products they replaced. They call tools, scan repositories, reason across files, and run multi-step loops. Inference costs for those workflows scale with context size and iteration count, not with the number of keystrokes saved. GitHub's per-seat pricing was always an abstraction over those real costs; the abstraction held while agentic usage was a small fraction of the total. It no longer is.

Flat-rate competitors including Cursor and Windsurf are now visibly picking up interest from developers shopping for predictability, though it is an open question how long any of them can hold that model as agentic usage grows across the industry. GitHub's gamble is that its integration depth, enterprise policy controls, and security posture are worth the shift to a metered bill. Its users are finding out in real time whether that case holds.

Sources cited:
- The GitHub Blog (Mario Rodriguez, April 27, 2026) (https://github.blog/news-insights/company-news/github-copilot-is-moving-to-usage-based-billing/)
- The Register (https://www.theregister.com/ai-and-ml/2026/06/02/github-copilot-users-threaten-exit-as-metered-billing-kicks-in/5249826)
- TechCrunch (https://techcrunch.com/2026/05/30/what-a-joke-github-copilots-new-token-based-billing-spurs-consternation-among-devs/)
- GitHub Community Discussion #192948 (https://github.com/orgs/community/discussions/192948)
- Visual Studio Magazine (https://visualstudiomagazine.com/articles/2026/04/27/devs-sound-off-on-usage-based-copilot-pricing-change-you-will-get-less-but-pay-the-same-price.aspx)