GitHub Copilot shifts to usage-based billing as agentic AI breaks subscription economics

GitHub Copilot shifts to usage-based pricing June 1 - but there's good news

Users who expect to see far higher prices already hate the deal. It's been an open secret that people haven't been paying anything like the full cost for their AI services. The bill's finally coming due. GitHub announced that as of June 1, 2026, all GitHub Copilot plans will shift to usage-based billing. This is a radical change from its current premium request unit (PRU) system. Going forward, users will consume monthly allotments of GitHub AI Credits based on token consumption, including input, output, and cached tokens at published API rates. In other words, GitHub is moving to a token-based pricing model. Smart people saw this coming. A week ago, GitHub blocked users from getting a new GitHub Copilot subscription. GitHub also began restricting the models available from its individual subscription plans, while dropping access to Opus models entirely. Price increases were clearly on their way. Why? According to GitHub, it's no longer the same service. What was once a smart programming editor has evolved into "an agentic platform capable of running long, multi-step coding sessions, using the latest models, and iterating across entire repositories." On top of that, "Agentic usage is becoming the default, and it brings significantly higher compute and inference demands." GitHub claims its current premium request model is unsustainable. After all, they stated, "a quick chat question and a multi-hour autonomous coding session can cost the user the same amount," with GitHub absorbing escalating inference costs. The usage-based model is intended to maintain long-term service reliability. The good news is that, for now, anyway, base subscription pricesremain unchanged. Copilot Pro is staying at $10 per month, and Pro+ is at $39 per month. However, these subscriptions will now include monthly AI Credits matching their dollar value. That is, Pro subscribers receive $10 in credits, while Pro+ users receive $39. I have no idea why GitHub felt the need to spell this out. Code completions and Next Edit suggestions will remain included without consuming AI Credits. Users on annual plans will continue with PRU-based pricing until expiration, when they transition to Copilot Free with upgrade options, or they can convert early to monthly plans with prorated credits. Copilot Business, $19 per user per month, and Copilot Enterprise. $39 per user per month, maintain their current pricing while adding equivalent monthly AI Credits per seat. To ease the transition, GitHub will provide promotional credits for June, July, and August 2026: Business customers receive $30 per month, and Enterprise users receive $70 per month. However, and this is important, in the past, when you ran out of PRUs, you simply downshifted to a less capable model. With the new AI Credits approach, when you're out of Credits, you're out of luck. If you want to keep working, you'll need to pay more for Credits. Organizations can benefit from pooled usage across teams, eliminating stranded capacity from individual unused credits. Administrators will gain budget controls at the enterprise, cost center, and user levels, with options to allow additional purchases or cap spending when included pools are exhausted. GitHub plans to launch a preview of the bills in early May. This will give you a look at your projected costs before the new June bills come due. Many users aren't waiting to dismiss this new pricing plan as a bad deal. As one Reddit poster put it, "I don't see companies going to be all happy if they get a 50x larger bill. People really underestimate how many tokens they use." Another shrugged, "They could've just shut down Copilot completely. Literally the only reason to stay is that you're familiar with it and are not ready to invest 30 minutes of your life to get familiar with Claude code, Codex, or whatever." For all the grumbling, though, it's not like the news is surprising. People who paid attention to AI's growing costs -- memory is more expensive than ever, and gigawatt datacenters don't build themselves -- knew this was coming. Other companies have already started to hike their rates. For example, OpenAI increased the cost for developers using its flagship GPT-5.2 model from $1.25 per input token in the previous GPT-5.1 to $5.75. In addition, Anthropic confirmed a de facto price increase for its Claude enterprise edition on April 15 when it moved from fixed pricing to a dynamic usage-based model. (Disclosure: Ziff Davis, ZDNET's parent company, filed an April 2025 lawsuit against OpenAI, alleging it infringed Ziff Davis copyrights in training and operating its AI systems.) Like it or lump it, the day of cheap AI is almost done. I expect costs to jump by 2 to 3 times by year's end, and I won't be surprised if prices end up far higher than that.

Microsoft's GitHub shifts to metered AI billing

Microsoft is closing the AI buffet offered to GitHub Copilot customers, acknowledging that it can't sell AI like Red Lobster's Endless Shrimp. The US seafood restaurant's all-you-can-eat shrimp promotion led the company to bankruptcy in 2024 and while Microsoft is nowhere near so financially overextended, the software giant's code hosting biz has decided it no longer wants Copilot to operate at a loss. GitHub is therefore shifting Copilot from request-based billing to usage-based billing on June 1, 2026. GitHub absorbed much of the escalating inference cost, but the current premium request model is no longer sustainable Under request-based billing, GitHub Copilot subscribers will be allowed to submit a set number of premium requests, with certain models priced at a higher request rate but without any consideration for the complexity of the request. So complex prompts that require a lot of "thinking" often cost GitHub more than the company earned in subscription fees. "Today, a quick chat question and a multi-hour autonomous coding session can cost the user the same amount," explained Mario Rodriguez, chief product officer on the GitHub product team, in a blog post. "GitHub has absorbed much of the escalating inference cost behind that usage, but the current premium request model is no longer sustainable." Under usage-based billing, there's a more direct correlation with metered tokens - sets of three or four characters that represent the basic economic unit for selling AI services. It's not quite as simple as $X for X tokens - different models meter tokens at different rates - so GitHub has devised a virtual currency unit called GitHub AI Credits that's worth $0.01. Copilot customers consume input tokens, output tokens, and cached tokens, each priced based on the model used. Microsoft converts that to a cost measured in AI Credits. "Instead of counting premium requests, every Copilot plan will include a monthly allotment of GitHub AI Credits, with the option for paid plans to purchase additional usage," said Rodriguez. "Usage will be calculated based on token consumption, including input, output, and cached tokens, using the listed API rates for each model." Knowing the outcome of this calculation in advance will be difficult - usage-based billing is non-deterministic, so users can never be sure how much time, and how many tokens, a model will consume to respond to a specific input. Different prompts may involve tools that complicate token consumption calculations. GitHub at least intends to try to give customers a hint of what's coming. Rodriguez said the company will introduce "a preview bill experience in early May, giving users and admins visibility into projected costs before the June 1 transition." AI companies were taken by surprise when OpenClaw attracted widespread attention in February, prompting a surge of experimentation with AI agents running 24/7 on various tasks. And the increasing competency of AI models around this time also encouraged more developers to explore AI coding. As a result, companies offering subsidized access to AI services through subscription plans faced more demand than they could satisfy with their inferencing infrastructure. The price correction that followed has been rippling across the industry. GitHub last week signaled its intent to stanch the red ink by suspending the creation of new Copilot, Pro, Pro+, and Student plans. Before that, Anthropic and Google took steps to limit some uses of its services. OpenAI responded by debuting a more expensive $100 subscription tier in an effort to boost usage of its Codex model, even as the company is contemplating an end to unlimited usage under subscription plans. Cloud providers like AWS and Azure have been dealing with capacity challenges too. GitHub's subscription rates will remain the same: Copilot Pro is $10/month, Pro+ is $39/month, Business is $19/user/month, and Enterprise is $39/user/month. At the $0.01 GitHub AI Credit rate, Copilot Pro subscribers get 1,000 AI Credits per month. Copilot Pro+ subscribers get 3,900. Once users exhaust the usage allowed under a plan, they can define an overflow budget - or just stop using AI until the next monthly billing cycle resets their AI Credit balance. Organizations and enterprises will receive 1,900 and 3,900 API Credits per user per month respectively. However, existing Copilot Business and Copilot Enterprise customers get a higher number of API Credits from June 1 through September 1, 2026, at 3,000 and 7,000 respectively. Users on annual subscription plans have the option to cancel and receive a pro-rated refund or to be downgraded to Copilot Free upon subscription expiration - those plans will not be renewable. Regardless, those riding their annual subscription plans to the bitter end will see prices skyrocket for premium models. For example, Anthropic's Opus 4.7, subject to a 7.5x multiple under request-based billing, will see its multiplier jump to 27 going forward. OpenAI's GPT-5.4 will see its multiplier rise from 1x to 6x. The new regime isn't entirely metered. Subscribers who reach their AI Credit limit can continue to access Copilot for code completions and Next Edit Suggestions - these services are unlimited on paid plans. That's more than you can say about Endless Shrimp, recently revived for a limited time only. ®

GitHub shifts Copilot to usage-based billing, signaling a new cost model for enterprise AI tools

The move reflects rising compute demands and agentic workflows, requiring CIOs to rethink budgeting and governance. GitHub is moving its Copilot coding assistant to a usage-based billing model, replacing fixed subscription pricing with consumption-based charges as demand for AI-driven development workloads increases. The change, announced in a company blog, will take effect on June 1 and will apply to Copilot Pro, Pro+, Business, and Enterprise plans. Under the new model, usage will be measured through "AI credits," reflecting the compute resources consumed during interactions with the service. "Today, we are announcing that all GitHub Copilot plans will transition to usage-based billing on June 1, 2026," Mario Rodriguez, GitHub's Chief Product Officer, wrote in the blog post. "Instead of counting premium requests, every Copilot plan will include a monthly allotment of GitHub AI Credits, with the option for paid plans to purchase additional usage."

Microsoft's GitHub suspends Copilot account sign-ups

Remember what we promised when you subscribed for a year? Well, we've got a new deal that's better for us. Microsoft's GitHub has stopped accepting new Copilot individual subscriptions while the code hosting biz figures out how it can meet its service commitments without breaking the bank. The code locker has paused signups for GitHub Copilot Pro, Pro+, and Student plans, wrote Joe Binder, VP of product, in a blog post on Monday, in order to help the company serve existing customers more effectively. "Agentic workflows have fundamentally changed Copilot's compute demands," said Binder. "Long-running, parallelized sessions now regularly consume far more resources than the original plan structure was built to support. "As Copilot's agentic capabilities have expanded rapidly, agents are doing more work, and more customers are hitting usage limits designed to maintain service reliability. Without further action, service quality degrades for everyone." Microsoft didn't say why it needs to implement this pause, but February's surge of enthusiasm for OpenClaw seemingly caught AI infrastructure providers unprepared for rising demand and struggling to keep up. Anthropic tried to reduce demand by adjusting its usage limits to shift consumption away from peak hours and enforcing its policy regarding use of third-party tools like OpenClaw. Google enacted a similar policy for its Antigravity AI development environment, Gemini CLI, and Gemini Code Assist. OpenAI undertook its own usage balancing earlier this month. Cloud providers have struggled to keep pace, too. AWS reportedly lost business to Google Cloud last year due to inability to meet AI demand. And Microsoft Azure has been having capacity troubles recently. GitHub too has been struggling with availability. The tech industry spent last year talking up software agents. But the infrastructure to support the proliferation of autonomous software and AI workloads remains a work in progress, and work on some of the data centers being built to handle the load has stopped, slowed or been abandoned. And now with Anthropic and OpenAI looking to go public, the leading model-makers are under pressure to make smaller losses - making expensive datacenter builds less appetizing. For GitHub, the most recent manifestation of the compute shortage involved suspending GitHub Copilot Pro free trials last week due to abuse. GitHub Copilot's free tier remains available. Now, as part of GitHub's cost cutting and service realignment, Binder said the operation will tighten usage limits for individual plans. GitHub Copilot imposes two forms of usage throttling: session and weekly limits, which are tied to token consumption and a model-specific multiplier. Session limits, according to Binder, help ensure that models remain available during peak usage. GitHub will be adjusting these "to balance reliability and demand," he said. Exceeding a session limit means waiting until the usage window resets before Copilot can be used again. Weekly limits cap the number of tokens a user can consume within a week. They were introduced, according to Binder, "to control for parallelized, long-trajectory requests that often run for extended periods of time and result in prohibitively high costs." A separate set of premium usage limits, introduced earlier this month, cap requests to high-end models. GitHub Copilot currently bills per request, which is any interaction the user has with Copilot, as opposed to per token. That flat rate - modified by model multipliers - can still end up costing Microsoft more than the company charges if the request ends up sending the backend model down an unexpectedly long chain of thought. These latest changes therefore reportedly reflect an effort to move toward token-based billing, and away from plans that offer flat-rate token consumption. As part of the transition toward more sustainable business practices, Binder said that Anthropic's Opus 4.5 and 4.6 models will be removed from Pro+ subscriptions. Opus 4.7, launched last week, will be available to Pro+, Teams, and Enterprise customers, in conjunction with a 7.5× premium request multiplier as part of promotional pricing until April 30th. The discontinued Opus 4.6 incurred a 3x premium. So the new option is more costly, at least on paper - although there may be processing efficiencies that help balance the higher cost for certain kinds of requests. Opus 4.7 expands more tokens than its predecessors, making it between 20 percent to 40 percent more expensive, though it performs better in certain scenarios. Copilot Pro and Pro+ subscribers have until May 20th to seek a refund if they're unhappy with the changes. That would be almost everyone voicing an opinion about the changes in the GitHub Community forum. ®

GitHub freezes new Copilot sign-ups as agentic AI breaks the economics

Agentic coding workflows are now routinely generating costs that exceed what users pay per month. GitHub's response, pausing new sign-ups for Pro, Pro+, and Student plans and tightening usage caps, signals that the era of unlimited AI assistance at fixed prices is ending. GitHub has paused new sign-ups for its Copilot Pro, Pro+, and Student plans and tightened usage limits across all individual tiers, citing a fundamental mismatch between how developers now use the product and the infrastructure it was built to support. The company's VP of product, Joe Binder, said in a blog post that agentic coding workflows, long-running, parallelised sessions in which AI agents and subagents tackle complex problems autonomously over extended periods, are now routinely consuming more compute than users pay for in a month. "It's now common for a handful of requests to incur costs that exceed the plan price," Binder wrote. The change, effective 20 April, leaves Copilot Free as the only plan still accepting new individual sign-ups. Existing users retain access to their current plans and can upgrade between tiers, but GitHub has given no timeline for resuming new subscriptions. Pro and Pro+ subscribers who contact GitHub support between 20 April and 20 May can cancel and receive a refund, with no charge for April. The usage changes that accompany the pause are structured to push heavier users towards the pricier Pro+ tier. GitHub is tightening both session and weekly token limits on individual plans, caps that govern how many tokens a user can consume in a given time window, separate from the premium request entitlements that determine model access. A user can have premium requests remaining and still hit a usage limit because the two systems operate independently. Pro+, at $39 per month, now offers more than five times the limits of the $10-per-month Pro plan. Usage warnings are being added to VS Code and the Copilot CLI so developers can see approaching limits before hitting them mid-workflow. Model access is also being restructured. Opus models, Anthropic's heaviest and most capable models, are being removed from the Pro plan entirely. Opus 4.7 remains available on Pro+. Opus 4.5 and 4.6, previously announced for removal from Pro+, are being removed from that tier as well. The pattern is straightforward: the most compute-intensive models are migrating exclusively to the most expensive individual tier. The economics behind the move are unusually candid for a Microsoft product announcement. Copilot was originally designed for code completion, short, stateless suggestions that consume modest compute per interaction. Agentic coding, by contrast, involves sessions that can run for hours, spawn multiple parallel threads, and generate token volumes that bear no resemblance to the autocomplete interactions that shaped the original pricing structure. GitHub's own Copilot features, including the /fleet command for parallel workflows, are now listed among the behaviours GitHub is asking its own users to limit. This is not the first sign of strain. The week before the sign-up pause, GitHub had already suspended Copilot Pro free trials due to abuse, a narrower measure that hinted at the broader capacity pressure to come. And the sign-up pause itself arrives at a politically awkward moment for GitHub with its developer user base. In late March, the platform came under significant backlash after developers discovered that Copilot had been inserting promotional "tips", including an advertisement for productivity app Raycast, into pull requests, in some cases appearing as if written by the developer rather than the AI. The feature was disabled the same day, with GitHub's VP of developer relations, Martin Woodward, saying the behaviour had become "icky" after Copilot's reach was extended to pull requests it hadn't created. GitHub described it as a programming logic issue, not an advertising strategy. More than 11,000 pull requests were affected before the rollback. The broader pattern, analysts say, is structural. Charlie Dai, vice president and principal analyst at Forrester, said the move shows how agent-driven coding is shifting workloads towards longer-running and parallel sessions that create higher and less predictable compute demand. "Cost structures built for lightweight assistance no longer hold," Dai said, "and this puts pressure on GPU capacity, reliability, and unit economics." He added that similar usage restrictions from major model providers suggest capacity rationing is likely to become a feature of the industry as agentic development becomes routine. For enterprise engineering leaders, Dai said the episode is a reminder to evaluate AI coding tools as metered infrastructure rather than unlimited productivity layers. Faisal Kawoosa, founder and chief analyst at Techarc, said the dynamic is a familiar one. "First you give users access to a tool with relatively open usage, and then gradually start defining limits as adoption grows," he said. Kawoosa added that the next step is likely to be more differentiated plans that create clearer monetisation opportunities, noting that GitHub's depth of integration into developer workflows gives it unusual leverage: "a developer can live without an email ID, but not a GitHub account." Whether competitors, including Claude Code, Cursor, and Codeium, can move quickly enough to absorb frustrated Copilot users before GitHub recalibrates its pricing structure is the open question the market is now watching.

GitHub pauses new Copilot sign-ups as agentic AI strains infrastructure

GitHub said long-running, parallelized AI coding sessions are pushing Copilot beyond the limits of its original individual plan structure, prompting tighter caps and a pause on new sign-ups. GitHub has paused new sign-ups for several individual Copilot plans and tightened usage limits, saying newer agentic coding workflows are consuming far more compute than its original pricing and service model was built to handle. The move is a reminder that as AI coding assistants grow more autonomous, vendors may have to balance developer demand against infrastructure cost and service reliability. "As Copilot's agentic capabilities have expanded rapidly, agents are doing more work, and more customers are hitting usage limits designed to maintain service reliability," GitHub said in a blog post. "Without further action, service quality degrades for everyone."

GitHub Copilot's price shakeup could end cheap AI coding as we know it

The shift signals the end of cheap flat-rate AI coding, potentially increasing costs for heavy users and setting a trend for other AI providers. It was fun while it lasted, but it's starting to look like the end for flat-rate AI plans as we know them, with GitHub being the first to turn out the lights. Just a week after announcing it was halting signups for its flat-rate Copilot Pro and Pro+ plans, Github has announced that starting in June, those plans will switch over to usage-based pricing. Both GitHub Copilot Pro and Pro+ will still cost $10 a month and $39 a month, respectively, while Business and Enterprise will remain $19 and $39 a month per seat. But beginning June 1, those plans will replace a fixed allotment of "premium requests units," which are based on a user's AI request count and adjusted based on the strength of the model, with "AI Credits," which are based on the actual tokens used during AI exchanges. Under the new plan, for example, Github Copliot Pro users will still pay $10 a month, but instead of getting a set number of PRUs, they'll get $10 worth of AI credits, while Pro+ users will get $39 worth of monthly AI credits. A similar AI credit allotment will apply for Business and Enterprise users. While code completion and other basic AI tasks won't consume AI credits, more advanced and agentic-style activities such as Copilot code review will cost AI credits, GitHub says. Users who spend all their AI credits before the month is up will have the option to buy more. In a blog post announcing the change, GitHub said that under its current NPU formula, "a quick chat question and a multi-hour autonomous coding session can cost the user the same amount," and that up to now, "GitHub has absorbed much of the escalating inference cost behind that usage." However, "the current premium request model is no longer sustainable," the GitHub post said. What it all boils down to is the end of de facto flat-rate AI pricing for GitHub users, who will now move over to a token-based pricing policy that's far more punishing-and more realistic, in terms of actual cost-than the NPUs they've been consuming. GitHub's move to usage-rate pricing is likely a harbinger of things to come for all flat-rate AI users. The truth is that the flat-rate plans from Anthropic, Google, and OpenAI have long been loss leaders, devised to grow their user bases and get new subscribers hooked on their AI-powered wares. Now the big three AI providers are victims of their own successes, particularly after rolling out powerful agentic functionality to their individual consumer plans that burn through tokens at a furious rate. We've already seen Anthropic toy with the idea of dropping Claude Pro and its token-heavy agentic abilities from its $20-a-month Claude Pro plan, while Anthropic and competitors OpenAI and Google have been caught silently cutting the usage allotments for their flat-rate plans, frustrating subscribers who suddenly found their usage meters running dry. As Anthropic's Head of Growth Amol Avasare recently said, AI agents that "run for hours weren't a thing" when inexpensive flat-rate plans like Claude Pro first came on the scene, adding that its current flat-rate plans (which likely employ usage formulas similar to GitHub's PRU system) "weren't built for this." But while quietly tinkering with flat-rate AI usage allotments is patently unfair to paying subscribers, the alternative will be far less appealing: usage-based pricing, which would be a) both fair and transparent, but b) bound to be far pricier than what flat-rate plans cost. Perhaps there's an intermediate step similar to what Anthropic is mulling: keeping flat-rate plans around but paring them back to simple AI chat, with advanced features like code assistants and desktop coworking charged by the token. Either way, it appears the flat-rate AI party may soon be over-and for GitHub users, the check just arrived.

GitHub pauses Copilot Pro sign-ups over rising compute costs

GitHub has paused new sign-ups for its Copilot Pro, Pro+, and Student plans, citing cost issues linked to agentic coding workflows. The change, effective 20 April, positions Copilot Free as the only individual plan accepting new users. Joe Binder, GitHub's VP of product, indicated that these workflows now consume more compute resources than users' monthly payments cover. "It's now common for a handful of requests to incur costs that exceed the plan price," Binder said. Existing users can maintain access to their current plans and have the option to upgrade, but GitHub has not provided a timeline for resuming new subscription offers. Pro and Pro+ subscribers can cancel between 20 April and 20 May to receive a refund, with no charge for April. The pause leads to tighter session and weekly token limits across individual plans, encouraging users to transition to the Pro+ tier. Pro+, priced at $39 per month, now offers over five times the limits of the $10 Pro plan. Usage warnings will be integrated into VS Code and the Copilot CLI to inform developers before they reach set limits. GitHub is also revising model access; Opus models, the most capable AI models, are being removed from the Pro plan. Opus 4.7 will remain available on Pro+, while Opus 4.5 and 4.6 will be removed altogether from both tiers. This shifting landscape reflects a larger trend where agentic coding sessions generate unpredictable computing demands. Repository features causing additional costs, such as the ability to run multiple parallel workflows, are also being restricted. Prior to this announcement, GitHub had suspended Copilot Pro free trials due to abuse, indicating underlying capacity pressures. The timing of the pause coincides with backlash over Copilot's insertion of promotional content into pull requests, which was disabled, affecting over 11,000 requests. Analysts suggest that GitHub's adjustments may prompt developers to view AI tools as limited resources. Faisal Kawoosa of Techarc noted a likely trend of more differentiated pricing structures as user demand evolves, maintaining GitHub's considerable leverage in the developer market. As competitors assess the situation, there is uncertainty regarding their ability to attract affected Copilot users prior to potential changes in GitHub's pricing strategies. "Cost structures built for lightweight assistance no longer hold," said Charlie Dai, a Forrester analyst, emphasizing the potential for more capacity rationing across the industry.