GitHub Copilot's fixed monthly subscription dies June 1. Starting that date, every Copilot request will cost exactly what it costs to run—one price for a quick autocomplete, a different price for a multi-hour autonomous coding session. GitHub's announcement frames this as fairness. The math says something else.
The current model charges every subscriber the same rate regardless of what their requests actually consume. A developer who asks Copilot to explain an error message pays the same as a developer who asks Copilot to refactor an entire codebase over several hours. GitHub says it has absorbed the difference for years. That ends in six weeks.
Power users—developers building agents, running autonomous loops, or treating Copilot as a coding co-pilot rather than a suggestion engine—will pay more under the new model. But they already cost GitHub more. The company is simply stop subsidizing their compute.
For casual users, the shift could mean lower bills. If you hit Copilot three times a day for quick fixes, you might spend less under true usage-based pricing than the current flat rate. GitHub hasn't released specific tiers yet, but the direction is clear: lighter usage gets lighter bills.
The deeper bet is about AI-native development. GitHub is signaling that it expects developers to integrate Copilot into more workflows, not fewer. Agents that plan, write, test, and iterate autonomously are becoming standard practice. Those workflows consume GPU time in ways simple autocomplete never will. By pricing per compute, GitHub stops losing money on its most engaged users while remaining accessible to the rest.
This is a rational move for a Microsoft-owned platform at scale. OpenAI, Anthropic, and Google have all moved toward token-based or usage-based pricing for similar reasons. The economics of transformer inference are brutal at scale—each query to a frontier model costs compute that users rarely think about. Flat subscriptions hide this cost until the bill comes.
Developers who rely on Copilot for deep, sustained sessions should start modeling what the new pricing might look like. GitHub will likely release cost calculators before June 1. The developers who prepare now will avoid surprises. Those who don't will find their favorite tool getting more expensive precisely when they use it most.
GitHub called the change "necessary to keep Copilot financially sustainable." That's honest. Sustainability, though, has winners and losers. The losers are the developers whose usage patterns look most like AI-native development—the exact workflows GitHub wants to encourage.