GitHub Copilot's new usage-based billing started on June 1, replacing the previous flat-rate subscription. Developers have reported using large portions of their monthly credits within hours, leading to widespread complaints and some threatening to stop using the product.
Each request is now priced dynamically, depending on the model used, request type, amount of submitted material, and response complexity.
Microsoft announced the change in April, noting that GitHub Copilot has evolved significantly over the past year. The company explained that it now supports more complex, agentic workflows that require greater computing resources.
What Changed With GitHub Copilot’s New Usage?Based Billing
Previously, GitHub Copilot used a flat monthly pricing model, charging $10 a m?onth for Copilot Pro and $39 a month for Copilot Pro+. This structure allowed users to make many requests across different AI models for a predictable fee.
Under the new approach, each request consumes credits from a monthly allocation. The cost per request now varies depending on several factors:
- The AI model chosen
- The type and complexity of the request
- The amount of context submitted
- The complexity of the response generated
Microsoft explains that this change brings pricing more in line with actual usage and costs, describing it as necessary for delivering a more sustainable and reliable product experience.
Why Developers Are Complaining About Copilot’s New Credit System
The response on GitHub's user forum and Reddit has been largely negative, mainly revolving around how quickly credits are used up and how unpredictable the per-request costs can be.
One developer on the $39 Copilot Pro+ plan shared that they used about 8% of their monthly AI credit allotment in just two hours, estimating that their 7,000-unit quota might run out in less than two days.
Another user reported spending more than $6 on a single change request, noting that the consumption was "impossible to predict." A Reddit user mentioned that a session using Claude 4.8 to fix website issues used 1,180 credits, which is about 16% of their monthly Pro+ allowance, for results they described as only mediocre.
The main concern expressed is that budgeting for AI usage is difficult when a single feature request can consume a significant portion of the monthly credits.
Developers Moving to Alternatives and How Microsoft Is Responding
Many users have mentioned plans to move their work to other services. Common options include accessing Anthropic and OpenAI models directly or routing requests through third-party services such as OpenRouter, RooCode, and LM Studio.
One user described a hybrid approach: using the Pro+ allocation until it runs out, then switching to OpenRouter for the rest of the month. OpenRouter operates within the same VS Code interface, offers a broader selection of models, and allows credits to roll over for up to a year, unlike the GitHub Copilot allocation.
A GitHub spokesperson confirmed the billing update to The Register, stating that usage-based billing is now active. The new pricing model for GitHub Copilot reflects actual usage and includes spending limits, usage dashboards, and model selection options to help users manage their costs.
The company also announced the launch of a higher-capacity tier called Copilot Max, aimed at users who require more extensive usage.
What Affected GitHub Copilot Users Can Do to Control Costs
Developers worried about costs under the new model have several options. They can set spending limits in the GitHub Copilot billing dashboard to control monthly charges.
- Monitoring the usage dashboard helps track credit consumption per request and per model. Choosing less expensive models for routine tasks can also help, with higher-cost models reserved for more complex work.
- Evaluating the new Copilot Max tier may be worthwhile if usage consistently exceeds the standard allocation. Some may consider third-party model access through services that offer rollover credits or lower per-request prices.
GitHub has not announced any changes to the new billing structure in response to recent feedback. The company emphasizes the use of spending limits and usage dashboards as the main tools for managing costs under the metered system.
Thank you for being a Ghacks reader. The post GitHub Copilot Usage-Based Billing Takes Effect, Drawing Developer Backlash Over Rapid Credit Depletion appeared first on gHacks.
0 Commentaires