Why did GitHub Copilot billing anger developers?

What changed

GitHub Copilot is moving from a flat, request-based billing approach to a usage-based model. As that pricing shift rolls out, developers say their costs can spike quickly—burning through a month’s worth of credits in just hours.

What developers are reacting to

Developers’ complaints focus on predictability and budgeting: Copilot usage no longer maps cleanly to a fixed subscription cost. Instead, usage and token consumption appear to drive the bill more directly, which can make team-level spend difficult to forecast—especially for developers who rely on Copilot heavily throughout the day.

Why it matters

This is a key moment for AI-assisted coding tools because pricing is effectively becoming part of the product experience. If marginal usage costs rise too steeply, organizations may:

• Limit who can use Copilot (or require approvals)
• Constrain usage to specific workflows or repos
• Push teams toward alternatives (or internal tooling)
• Reassess whether Copilot is cost-justified versus writing code without assistance

The broader signal

GitHub Copilot is one of the most mainstream developer AI products. When billing changes create widespread friction, it can influence how other vendors structure pricing for LLM-based developer tools—potentially accelerating a shift toward metered models, cost controls, and “AI governance” practices inside engineering orgs.

In short: the anger is largely about the move to metered usage billing and the resulting mismatch between heavy coding habits and how developers expected to pay.