GitHub took a tool developers loved, replaced the flat fee with a meter, and acted surprised when the bill came back with the word "joke" attached. That's the whole story. Everything else is detail.
Copilot moved to a token-based billing model in early 2026, charging users by the number of tokens its AI processes rather than a predictable monthly rate. Developers responded by widely criticizing the change, with some calling the new pricing a "joke". The complaint isn't really about money. It's about being asked to trust a number you can't see being counted.
A meter is not a subscription
Copilot used to be one line on a corporate card. A flat monthly subscription fee, predictable, boring, easy to defend to a finance team. Then it became a variable. Every autocomplete, every chat, every refactor suggestion is now a tiny invisible withdrawal from a balance you didn't quite agree to.
The primary concern from users, per Ars Technica's reporting, is the unpredictability and lack of transparency around how tokens get consumed. That phrasing is polite. The actual experience is sitting at a keyboard wondering whether asking the assistant to explain a function just cost three cents or thirty.
Anyone who's ever opened an AWS bill knows the feeling. Metered pricing is fine when you're a backend service architect with a spreadsheet. It is not fine when you're a developer trying to think.
The trust isn't coming back
Here's the part GitHub seems to have missed. TechCrunch's coverage put it bluntly: critics argue the change shifts financial risk to developers and erodes trust. Erodes is doing a lot of work in that sentence. Trust between a developer and their tooling is not a sentiment. It's a workflow assumption.
Flat pricing said: use me as much as you want, we figured it out on our end. Token pricing says: every keystroke is a transaction, please optimize accordingly. Those are two different products. They produce two different relationships.
And once a developer starts second-guessing whether to invoke the assistant, the assistant has already lost. The whole pitch of Copilot was friction removal. Adding a mental cost calculator on top of every prompt isn't a pricing tweak. It's a feature regression sold as a billing update.
Why this keeps happening
GitHub isn't being uniquely cynical. They're being normal. Every AI tool provider is staring at the same compute bill from the same handful of model vendors, and every one of them quietly knows the flat-rate math doesn't work at scale. Power users cost more than they pay. Casual users subsidize them. The spreadsheet wants tokens.
Fine. But there's a difference between needing to change pricing and pretending the change is neutral. Multiple outlets, including The Verge, Ars Technica, TechCrunch, and ZDNet, covered the developer outcry in February, showing developers noticed the change immediately and were not gentle about it.
The lesson sitting in plain sight is that AI tooling cannot be priced like AWS and marketed like Spotify. You either commit to the meter and give people a real-time dashboard, hard caps, and a kill switch — or you commit to the subscription and eat the variance. Doing both at once is how you end up as a verb in a Hacker News thread.
Copilot will survive this. GitHub is too embedded, the product is too sticky, and most enterprise buyers will grumble and renew. But the next time a competitor shows up with a flat fee and a straight face, a lot of developers are going to remember what it felt like to watch their editor turn into a taxi meter.
