GitHub Copilot AI Credits billing went live June 1, removing fallback models and triggering developer cost alarms
GitHub's shift from premium request units to token-based "AI Credits" billing took effect June 1, 2026 at the start of the billing cycle. Developers who rely on Copilot for agentic, multi-step coding sessions are now seeing projected monthly costs that far exceed their previous flat-rate bills.
What
GitHub announced the billing transition on April 27, 2026. Per the GitHub blog post by CPO Mario Rodriguez, every Copilot plan moved from counting premium request units (PRUs) to consuming credits calculated from token usage, including input, output, and cached tokens at published API rates.
Base subscription prices did not change with the transition. Per the April 27 billing post, Copilot Pro stays at $10/month, Pro+ at $39/month, Business at $19/user/month, and Enterprise at $39/user/month. Code completions and Next Edit Suggestions remain included in all paid plans and do not consume credit balances.
Two structural changes hit on June 1 that go beyond pricing units. First, the fallback model option was removed. Under the PRU system, a user who exhausted premium requests could continue working on a cheaper model. Per the official FAQ thread, users who exhaust credits now must wait for the monthly reset, purchase additional usage, or upgrade. Second, GitHub confirmed in the FAQ that free models are no longer part of the offering under usage-based billing, and that unused credits do not roll over from month to month.
Business and Enterprise customers receive temporary promotional credits. Per the April 27 billing post, Business accounts get $30 in monthly AI Credits for June, July, and August (vs the standard $19 base), and Enterprise accounts get $70. Monthly Pro and Pro+ subscribers migrated automatically. Annual subscribers remain on PRU-based pricing until their plans expire, at which point they move to Copilot Free unless they select a new monthly plan. Per the official FAQ, GitHub is retiring annual plans going forward.
Why it matters
The shift ends flat-rate billing for agentic Copilot use. For developers whose work stays within code completions and short chat interactions, the practical impact is limited since those features remain outside the credit system. For developers running Copilot in agent mode, multi-repository sessions, or long autonomous coding tasks, every token now carries a cost.
The removal of the fallback model option is the sharper edge. Previously, heavy PRU consumers could keep working at reduced capability when limits were hit. Now the same session simply stops until credits are replenished or reset.
Per secondary reporting from how2shout and dataconomy, developers sharing projected bills in public forums estimated monthly costs jumping from roughly $29 to $750 and from $50 to $3,000 for agentic-heavy workflows. GitHub has not independently verified those estimates, and the figures reflect individual developer projections rather than actual billed amounts on June 1. They do reflect the concern inside the developer community that token costs at current API rates, applied to sustained agent sessions, can compound quickly.
Rodriguez wrote in the April 27 announcement that flat-rate pricing had become structurally unsustainable: "Today, a quick chat question and a multi-hour autonomous coding session can cost the user the same amount." GitHub has not announced any cap mechanism, credit-rollover policy, or session-cost estimator in response to the backlash.
Context and reactions
Per secondary reporting from how2shout and dataconomy, developer migration discussions in public forums named Claude Pro, OpenAI Codex, DeepSeek, and local open-source models as alternatives for workloads where token costs now exceed the Copilot bill. GitHub has not released data on subscription cancellations or plan downgrades since April 20.
GitHub VP of Product Joe Binder had acknowledged disruption in an April 20 post that paused new individual sign-ups: "We know these changes are disruptive, and we want to be clear about why we're making them." That pause on Pro, Pro+, and Student sign-ups remains in effect as of June 1. GitHub said in the April 27 post that limits would loosen once usage-based billing took effect, but has not announced a reopening date.
The token model itself aligns Copilot with how Anthropic and OpenAI already price their developer APIs. For enterprise buyers already managing token budgets on those platforms, the structure is familiar. The difference is that Copilot's core competitive positioning was built on unlimited completions at a flat monthly price, and the agentic layer now operates on a different cost logic than the completion layer.
What to watch next
First billing statements under the AI Credits model will arrive in July for monthly subscribers. That is when the developer community will see actual billed amounts rather than projected estimates, and when any budget overage patterns will become concrete. GitHub has said it plans to provide usage tracking via the Billing Overview page on github.com.
Watch for GitHub to announce a reopening of individual plan sign-ups, which the April 27 post described as tied to the billing transition taking effect. A cap mechanism or session-cost preview tool would also address the most common developer concern surfaced in public forums since April 20.
Developers comparing plans under the new model can review current Copilot options at /go/copilot.
Sources
- GitHub Copilot is moving to usage-based billing: GitHub company blog, April 27, 2026, primary
- GitHub Copilot usage-based billing FAQ: GitHub community discussion, primary
- GitHub Copilot Switches to Token-Based Billing Today: Some Developers Fear Costs Will Skyrocket: how2shout, June 1, 2026, secondary
- Microsoft Switches GitHub Copilot To Usage-based AI Token Billing: dataconomy, June 1, 2026, secondary