GitHub users are staging a revolt against Microsoft’s new usage-based billing policy for its Copilot AI tool, reporting that their monthly credit allowances are being depleted in a matter of hours. According to www.theregister.com, the change, which went into effect on Monday, replaces predictable flat-rate subscriptions with a dynamic model that charges based on compute complexity, model selection, and the volume of data processed.
Frustrated developers have taken to GitHub’s community forums and Reddit to share stories of rapid credit exhaustion. One user paying for the $39-per-month Copilot Pro+ plan reported burning through 8 percent of their total monthly allowance in just two hours. Another developer noted that a single request to fix a project issue cost them more than $6 in credits.
“This is a staggering shift from a 'predictable subscription' to a 'stressful meter-based' service that hinders my productivity rather than helping it,” one developer wrote on the GitHub forum. Another user, who attempted to use the tool for minor site edits, reported a similarly negative experience: “It gave some pretty mediocre suggestions... Then I checked the actual usage page. 1,180 credits used. 16% of my monthly Pro+ allowance. Gone. For basically nothing.”
Microsoft defends move to usage-based costs
Microsoft maintains that the change is necessary to sustain the evolving nature of its AI offerings. In an April blog post, the company argued that Copilot is no longer the same product it was a year ago. The firm stated that today's service powers "far more complex, agentic workflows that consume far more compute," and that the new billing structure aligns costs with actual usage and value.
However, the explanations have done little to appease the user base. The outlet reported that many professionals are now vocalizing plans to migrate their workflows to competitors such as Anthropic and OpenAI. Others are seeking workarounds using third-party services like OpenRouter, LM Studio, or RooCode to maintain access to AI-assisted coding within their familiar VS Code environments.
One developer explicitly outlined their exit strategy: “I’ve opted to stick to Pro+, burn through my allocated credit in a week, and then pivot to using OpenRouter for the remainder of the month.” The move to dynamic pricing comes at a time when business users are increasingly sensitive to the unpredictable costs associated with integrating large language models into their daily development pipelines.
