GitHub GitHub Copilot's Metered Billing Is Burning Through Developers' Credits Fast
GitHub switched Copilot to usage-based AI Credits billing on June 1. A week in, developers are reporting that agentic workflows eat through monthly allowances in hours. The community backlash thread has nearly 1,000 thumbs-down reactions.
GitHub switched Copilot from a flat subscription to metered billing on June 1, replacing premium request units with “AI Credits.” One week in, developers are not happy.
The credit system prices each request dynamically based on which model you used, how many tokens went in, how many came back, and whether any were cached. Code completions and Next Edit suggestions are excluded and don’t consume credits. Everything else does. Each plan gets a monthly credit allocation that matches its dollar price: $10/month for Pro gets $10 in credits, $39/month for Pro+ gets $39 in credits.
How Fast Credits Are Disappearing
The problem is how quickly those allowances run out when agents are involved. Reports from the GitHub community forum and Reddit describe burning through double-digit percentages of a monthly budget in a few hours:
One developer on Pro+ ($39/month) reported losing 16% of their monthly allocation on a single request that produced poor results. Another said their $39 plan would run out in under two days at normal usage. A feature request using one of the higher-tier models cost over $6 in a single interaction.
Agentic workflows are the main culprit. When an agent reads files, writes code, runs checks, and iterates, each step consumes credits. A task that would have felt “free” under the old unlimited model now has a running tab.
The GitHub community discussion thread on the billing change has accumulated roughly 958 thumbs-down reactions against about 24 thumbs-up. GitHub has not announced a rollback, revised credit allowances, or any pricing adjustment. The company’s stated position is that usage-based billing aligns pricing with actual costs and helps maintain service reliability.
GitHub’s Rationale
In the official blog post, GitHub said Copilot “is not the same product it was a year ago” and that flat billing created problems for heavy users: “Usage-based billing fixes that. It better aligns pricing with actual usage, helps us maintain long-term service reliability, and reduces the need to gate heavy users.”
That last part is the argument: under flat billing, GitHub was limiting access through request caps and model gates to keep costs manageable. Usage billing is the alternative.
What Developers Are Switching To
Developers in the community thread are discussing alternatives including direct API access through Anthropic or OpenAI, Cursor, RooCode, and OpenRouter. Some are turning off agent features in Copilot entirely to preserve credits for inline completions.
GitHub added spending limits and a real-time credit dashboard so users can monitor usage and set hard caps before they overspend. Business and Enterprise customers are getting promotional credits ($30 and $70 extra respectively) through August while they adjust to the new model.
Sources: GitHub Blog, The Register, Visual Studio Magazine, TechSpot