The GitHub Copilot Bill Came Due. Here's What Engineering Leaders Should Do.
Kilo Blog
SubscribeSign in
The GitHub Copilot Bill Came Due. Here's What Engineering Leaders Should Do.<br>We said the era of free compute was ending. It ended on June 1 - and the people holding the bill are enterprise teams.
Job Rietbergen<br>Jun 05, 2026
Share
Right now, as I write this, our team is on the floor at the Gartner Summit, and there’s one conversation happening in every hallway and coffee line: what just happened to our GitHub Copilot bill?<br>It’s the trending topic of the day for a reason. On June 1, Copilot’s usage-based billing went live for everyone, and the people feeling it hardest are software engineering leaders who woke up this week to discover that a line item they’d treated as fixed for three years is now a variable cost that swings with their team’s most productive days.<br>A few weeks ago, we wrote that this was coming - the era of subsidized, all-you-can-eat AI was over, and the only honest path forward was paying for what you use. And it’s happening this week.<br>What we’re hearing on the floor
This isn’t just our read in a vendor blog. Many engineering leaders we’ve talked to this week are in the same scramble: how to get ahead of a bill that’s suddenly a moving target.<br>What actually changed
GitHub has moved from seat-based pricing to an access-plus-consumption model: your subscription funds a monthly credit pool, and you pay for everything beyond it.<br>Copilot now bills by GitHub AI Credits , calculated on token consumption - input, output, and cached - at per-model API rates. Code completions and Next Edit Suggestions stay free and unmetered, so if autocomplete is your whole workflow, little changes. But everything agentic - chat, agent mode, multi-step sessions, tool calls - is now metered, and Copilot code review now also burns GitHub Actions minutes on top of credits. Once your allowance is gone, you pay overage, or you’re cut off.<br>The real problem is that nobody can predict the bill
Teams can plan around a higher bill. What they can’t plan around is one that swings unpredictably from one week to the next - and that’s what most of this week’s complaints are really about.<br>Developers are watching credits evaporate in ways they can’t anticipate. One Pro+ user burned through roughly 8% of their monthly allotment in two hours and projected the whole thing gone in under two days. Another spent more than $6 on a single change request and called the consumption impossible to predict. A session using Claude 4.8 to fix some site issues ate 1,180 credits - about 16% of a Pro+ monthly allowance - for results the developer called mediocre. One person watched a single file review, with no code changes, consume 20% of their monthly allowance. At the org level, people are circulating projections of monthly costs jumping from $29 to $750, and from $50 to $3,000 in heavy agentic workflows. A “Goodbye, Copilot” post has been shared thousands of times, and TechCrunch called it the end of Copilot’s golden age.<br>The r/github thread that’s been climbing all week reads the same way, and the sharpest complaints aren’t about price at all. One developer described being forced into “token anxiety,” micromanaging every click to survive the month. Another nailed the unit mismatch: you bought a seat, and now every agentic run feels like “leaving a taxi meter running in another room.” And this one should land for anyone who signs off on a budget - a developer whose org hadn’t even finished configuring its credit pools wrote that, at his burn rate, “finance will be getting a hefty bill because management isn’t up to date on plan changes.”<br>To be precise: this isn’t a hidden markup. Copilot charges standard per-model API rates - one commenter noted the models cost “exactly the same price as direct from OpenAI and Anthropic.” The price was never the subsidy - the flat subscription was. Now that it’s gone, you’re just seeing what agentic coding actually costs.<br>Here’s the kicker for anyone responsible for a budget: you couldn’t even trust the preview. GitHub’s Billing Preview tool was meant to estimate costs before the switch - but it runs on discounted credits, so the number it showed enterprises is lower than what they’ll actually pay. GitHub also warns that older IDE and extension versions can display inaccurate pricing. And some heavy users found the projected spend wildly higher than their lived experience.<br>Either way, many couldn’t get a number they trusted.<br>This is already happening at enterprise scale
The individual horror stories are the visible edge of something bigger: at the org level, agentic coding is outrunning the budgets attached to it.<br>Uber is the clearest example. It burned through its entire 2026 AI coding tools budget in four months - by April - and has since capped employee spending at $1,500 a month. Its CTO for Mobility and Delivery, Praveen Neppalli Naga, confirmed the blowout to The Information. And it wasn’t even...