GitHub Copilot's Usage-Based Billing Is Six Weeks Old — Here's Who Got Burned
Six weeks after GitHub Copilot switched to usage-based billing, the invoices are in. 7% of developers saw $300-750 in overage, 2% blew past $750. The flat-rate AI buffet is closing — here's what every AI builder needs to learn from the backlash.

The first invoices landed in inboxes around June 30. Developers opened them expecting the familiar $10 or $39 line item. What they found instead was a number that, in some cases, had a comma in it.
GitHub Copilot's switch to usage-based billing went live on June 1, 2026. The company announced it in April (Mario Rodriguez, CPO, framed it as a sustainability move), but most subscribers didn't run the maths until the billing cycle closed. When they did, Reddit's r/GithubCopilot, r/ChatGPTCoding, and the GitHub Community forum erupted. One thread on the official announcement sits at 958 downvotes against 24 upvotes. TechCrunch ran with the headline "What a Joke." The Register documented mass cancellation threats.
Six weeks in, the pattern is clear. This is not a GitHub story. It is a crystal ball for every AI-powered product you pay for.
## What actually changed?
The old model was simple. Pay $10 a month for Copilot Pro, or $39 for Pro+, and use it as much as you wanted within a monthly request allowance. The allowance was generous enough that most people never thought about it. The $10 plan worked like Netflix for code: flat fee, unlimited consumption.
Under the new system, base prices stayed the same. Pro is still $10, Pro+ still $39, and the new Copilot Max tier costs $100. But those prices now buy you a bucket of "AI Credits" rather than access to the product. One credit equals one US cent. Pro includes 1,500 credits ($15 worth). Pro+ includes 7,000 ($70 worth). Max includes 20,000 ($200 worth).
Credits are consumed based on token usage (input, output, and cached) at per-model API rates. When the bucket runs dry, you either stop using premium features or you pay for overage. And the spending cap that stops overage charges is off by default. You have to go into Settings, find the toggle, and switch it on yourself.
Code completions and Next Edit Suggestions remain free and unlimited. Everything else (chat, agent mode, code review, CLI, cloud agent) now has a meter attached.
## How bad did it actually get?
Here are the numbers from 340 developer self-reports across Reddit, X, and the GitHub Community Forum in the first week of June.
Forty-one percent of developers saw no cost change. These are autocomplete users who occasionally open chat. Their bill barely moved.
Another 33% landed in the $20 to $100 range in additional costs. Regular chat, some light agent mode. Manageable, if annoying.
Seventeen percent hit $100 to $300 in extra charges. Daily agent mode, code review enabled on every PR.
Seven percent got slammed with $300 to $750. Heavy agent mode against mid-to-large codebases, using expensive models like Claude Opus or GPT-5.5.
And 2% blew past $750. These are developers running automated pipelines through Copilot's API, or teams that had agent mode embedded in their workflow before realising what it cost.
David Ramel at Visual Studio Magazine was in the worst cohort on day one. He burned through 1,227 of his 1,500 Pro credits (82% of his monthly allowance) in a single day. The culprit was a formatting agent that went off the rails. He projected a $180 bill.
Specific horror stories: One Pro+ subscriber burned 822 credits (54% of a monthly quota) on a single request. Another watched four agentic sessions consume 3,707 credits in a day. A developer on Reddit estimated costs going from $29 a month to roughly $750. Another posted a screenshot projecting $50 to $3,000. One GitHub Community user upgraded to the $100 Max plan after burning through Pro+, then exhausted all 20,000 Max credits in under 24 hours.
## Was the old model just a giant subsidy?
Yes. And Theo from t3.gg proved exactly how giant.
In May 2026, before the pricing change took effect, Theo ran an experiment. He took his comped Copilot Pro+ plan, spun up 50 concurrent sessions on a remote machine, and fed them unsolvable cryptography puzzles with the instruction "keep going until you find the answer." One session lasted 16 hours and 10 minutes, consuming 111 million input tokens and 1.6 million output tokens.
His estimate: between $15,000 and $46,000 in inference compute consumed on a single $40 monthly subscription. At one point, having used less than 5% of his message allowance, he had already cost Microsoft over $600 in actual inference spend. "Selling messages is a suicide mission," he said, "because a message does not equate to a specific amount of money."
Theo's take matters because he runs T3 Chat, an AI subscription product, and went through exactly the same maths. When his platform added Claude Sonnet, a small group of users burned $2,000 in five days. He had to slash limits and eat the subscriber backlash. His verdict on Copilot's pricing change: "This isn't a rug pull, you're just stupid. The only mistake GitHub made was taking too long to change the billing."
GitHub's old model was absorbing staggering losses on heavy users while collecting $10 a month. That was never going to survive agentic coding. The economics don't work when one user's single session costs more than their entire annual subscription.
## Who got burned worst?
Daily agent mode users are the obvious answer. These are developers who built their workflow around Copilot's most powerful features (multi-file refactors, autonomous debugging, repository-wide changes). GitHub spent 18 months marketing agent mode as the future. These users adopted it exactly as intended. They are the 7% now facing bills of $300 to $750 a month.
The maths is straightforward. A single agent session reading 30 files, generating 500 lines, and running two test iterations burns roughly 80,000 to 120,000 tokens. On Claude Opus 4.8, that session costs about $1.50. Ten sessions per working day across 22 working days: $330 in AI Credits, on top of the $39 plan fee.
But the group I find most interesting is the code review sleepers. Copilot's automated code review feature runs a full model pass on every PR. Developers who enabled it once and forgot about it discovered it was quietly accumulating credits in the background. A 500-line PR review costs roughly $0.50. At 15 PRs per day, that's $165 a month from code review alone, without ever opening the chat panel. The billing dashboard doesn't break this out by feature unless you enable the detailed view, so most people had no idea it was happening.
## What does this mean for every other AI tool you use?
Copilot is the canary. The same economics apply to every product that wraps AI models behind a flat subscription.
Anthropic has already started charging large Claude Enterprise customers for actual compute rather than offering subsidised tokens. OpenAI introduced a $100-per-month tier and is reportedly evaluating the end of unlimited usage. The flat-rate AI buffet is closing everywhere, not because companies are greedy, but because the underlying inference costs are real and variable in a way flat-rate pricing cannot absorb at scale.
For no-code builders, the lesson is urgent. If your app integrates AI features (an assistant, content generation, automated workflows), the cost of those features is almost certainly going to be metered on your end. You need to model for that. The days of shipping an AI feature and forgetting about it are over. Every prompt your users fire has a price attached, and somebody has to pay it.
This is where the architectural decision matters. The tools that abstract AI costs into the platform layer (where the provider owns the model calls and bundles them into a predictable subscription) have a real structural advantage. When you're on a flat-rate no-code platform and the platform handles the AI inference behind the scenes, you don't lie awake wondering whether a single formatting agent is about to torch your monthly budget. The risk is on the platform, not on you.
## The takeaway
GitHub Copilot's billing change wasn't a mistake. It was an inevitability that arrived six weeks ago and will repeat across the industry for the next two years.
If you're a developer who uses Copilot heavily, go to your billing settings right now and set a hard spending cap. The toggle is off by default and there is no ceiling without it. If you're a heavy agent mode user, do the maths on whether Claude Code's $100 flat rate or Cursor's $20 subscription is cheaper than your current credit burn.
If you're building a product that depends on AI features, the Copilot backlash is your advance warning. The era of unlimited AI for a flat monthly fee is ending. Your pricing model needs to account for that, either by building in headroom for metered costs or by choosing platforms that absorb the inference risk on your behalf.
Want to read
more articles
like these?
Become a NoCode Member and get access to our community, discounts and - of course - our latest articles delivered straight to your inbox twice a month!
