GitHub Community
All GitHub Copilot plans are now on usage-based billing #197089
Replies: 350 comments 546 replies
-
|
So the answer is basically: if you hit your limit too quickly, you should upgrade and pay more? I get why GitHub moved to usage-based billing, but the numbers feel way off compared to the previous system. I had only two short sessions in the VS Code extension, with maybe 2–4 prompts total, and somehow that already consumed 210.5 AI Credits/Tokens/Whatever. Under the old model, that kind of usage would barely make a dent in my monthly quota. Now it feels like a handful of normal interactions can burn through a noticeable percentage of the month's allowance. What worries me, and most of the users, isn't paying for usage. It's not knowing what a few everyday prompts are going to cost. If developers can't reasonably predict their consumption, it's hard to trust Copilot as a tool they'll use throughout the month. Honestly, this feels like the kind of change that pushes people to look at other providers or even go directly to the model vendors instead of using Copilot as their main AI tool. More transparency around how credits are consumed in real-world VS Code workflows would go a long way. |
Beta Was this translation helpful? Give feedback.
-
|
This change made it so much more expensive to do anything with it. I moved to just using chatgpt codex, it's only a little less user friendly, but you get so much more credits, and the models do a good job still. |
Beta Was this translation helpful? Give feedback.
-
|
I think they are linking the Pro usage to Pro+ |
Beta Was this translation helpful? Give feedback.
-
|
I had 300 Premium requests included in the university teacher program (enough for 14 days of vibing), now it's Credits. Noticet after 50 % usage warning after 2 hours of vibing. It eats tokens like a Dodge Ram gas. "Good job" MSFT! |
Beta Was this translation helpful? Give feedback.
-
|
I just used up 30% of my monthly quota on a simple renaming task on a small python application. This is price gouging at its finest. I for one will not be upgrading my account to get more credits and instead will be cancelling it. This used to be a great tool that I looked forward to using but now has deteriorated to a baseless money grab. Thanks, Microsoft and GitHub, I will not be recommended your products going forward. |
Beta Was this translation helpful? Give feedback.
-
|
after 6 days of light use |
Beta Was this translation helpful? Give feedback.
-
|
My GitHub account is associated with Fu-Jie, and I have been a long-time annual subscriber. My annual membership was originally set to expire in approximately two months. Earlier today (June 1, 2026), I clicked the "Refund" button in my account settings out of curiosity—not with the intention of immediately cancelling. I expected this action would lead to a confirmation page, not process the refund directly. However, the refund was executed immediately without any secondary confirmation prompt. I believe this is a design flaw in the refund workflow. Any action affecting payment and subscription status should include an explicit confirmation step to prevent unintended consequences from accidental clicks or exploratory actions. The absence of this basic safeguard led to the unexpected cancellation of my membership. To clarify: My request is not about renewal, but about the value of my current active contract. My existing membership had not yet expired and still had nearly two months of service remaining. Given recent changes to GitHub's billing policies, the terms and benefits under my current contract hold unique value during this remaining period. Once refunded and cancelled, renewing would not provide the same conditions. Given the above, I request that my original membership status and expiration date be restored, and I strongly recommend that your team improve the refund process by adding a necessary confirmation step. I look forward to your reply. |
Beta Was this translation helpful? Give feedback.
-
|
Eu também fiz isso no passado e ocorreu o mesmo, eles nem perguntam, te cancelam na hora. Muito louco isso. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Fu-Jie, Thank you for writing in and explaining the situation. We understand from what you shared that clicking the refund button processed immediately without a confirmation step, and that this was not your intent. We appreciate you flagging this as a UX concern. I've noted this feedback and shared with internal teams for investigation. Regarding restoring your previous subscription: this falls outside what I'm able to action directly. We cannot resolve account related issues in this public forum, and I'm sharing this information with the appropriate team to review whether your original subscription and expiration date can be reinstated. I'll follow up once I have more information. Thank you for your patience. |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
one afternoon pro+ limit 85% 
|
Beta Was this translation helpful? Give feedback.
-
|
Yes here same 2 days work 7K credits burned.. god bye GitHub.. you are not more payable, and its close to robbery! besides Copilot keeps you busy after restart to fix the VS again.. +its a shame thins so many developers here put things for free with all there know how, which get robed too. Years a go GIT was relay good now its just a massive rib-off...very sad! |
Beta Was this translation helpful? Give feedback.
-
|
I was a Github Copilot beta tester, then one of the first paying for the service. I was an evangelist of Github Copilot. Today I canceled my subscription. I am switching for Antigravity and Claude, and I am also considering testing how good the new Cursor is. |
Beta Was this translation helpful? Give feedback.
-
Same here the costs are exploding in just a couple of days. It is expected that some raises are necessary but these exceptional higher use of the Agents models and costs are way out of balance |
Beta Was this translation helpful? Give feedback.
-
did the same |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Subject: Large day-to-day difference in Copilot usage for similar work Hello, I am reporting a large difference in Copilot usage between two recent sessions on the same repository. On 2026-05-31, I was able to work through a long session and the usage remained within a range that felt predictable. On 2026-06-01, a session that felt comparable or smaller in visible scope consumed much more of my quota. From my point of view the difference is easy to verify and does not match the apparent amount or difficulty of the work performed. I understand that internal context, tool payload, or other service-side factors may exist, but the current accounting behavior is not transparent enough for planning real project work. Please clarify whether the accounting model changed or whether hidden context growth is being billed in a way that users cannot see. I can provide screenshots, approximate session times, and a short written comparison of the two sessions. 8 hours not heavy work... Regards, |
Beta Was this translation helpful? Give feedback.
-
|
It is disappointing to see the response to these concerns shift into a 'blame game' where users are essentially told they have a 'skill issue' for not optimizing tokens, rather than GitHub providing a transparent, predictable estimation model before requests are run.As it stands, the 'integration' advantage doesn't justify the cost or the lack of predictability. For my personal work, I’m moving to Codex and exploring other providers immediately. |
Beta Was this translation helpful? Give feedback.
-
I hope you realize that Codex will do the same as well if they get the huge amount of transferred users. The old rates were simply massively underwater financially and MS has drawn a line. |
Beta Was this translation helpful? Give feedback.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
-
That is a "them" issue. They should not have made a product with high value, low cost, tie it into systems that a majority of developers use, push it at every turn, then yank the proverbial rug out saying "Oops! Too expensive." |
Beta Was this translation helpful? Give feedback.
-
I mean, it's immoral but also entirely predictable and a classic business strategy. You were effectively all on a discounted preview. If you look at API costs on any frontier model, it is obvious MS was eating over 90% subsidy here. MS may live on a mountain of money but the board would never approve of this forever. |
Beta Was this translation helpful? Give feedback.
-
|
Dumbest decision ever.... |
Beta Was this translation helpful? Give feedback.
-
|
Guess what? It's called effective management, hah |
Beta Was this translation helpful? Give feedback.
-
|
I upgraded to GitHub Pro ($48/year) but downgraded it back to Free because I cannot subscribe to Copilot at this time. |
Beta Was this translation helpful? Give feedback.
-
Switch to claude code |
Beta Was this translation helpful? Give feedback.
-
|
but at the new consumption rate, that should give you about two days worth !!! |
Beta Was this translation helpful? Give feedback.
-
|
Hm, wondering if there will be similar changes for the many Copilot variants in M365 and general Microsoft products in the future. |
Beta Was this translation helpful? Give feedback.
-
|
@DanielRuf 👋🏻 Thanks for the question. Our team here supports GitHub Copilot specifically, and we don't have visibility into billing plans for Microsoft 365 Copilot or other Microsoft products. For questions about M365 Copilot, Microsoft's product and support channels would be the best resource. I am assuming this was posted in jest, but answering with added context for you or any other users where the info may be helpful. |
Beta Was this translation helpful? Give feedback.
-
|
I had faith in you.. Honestly, I regret not taking the refund offer you made. I genuinely think you're going to lose at least 80% of your client base. This is so ridiculous. It's far better to pay in real money and not by token. The base usage is ridiculously low. |
Beta Was this translation helpful? Give feedback.
-
I hear you.. Sound like a trap indeed. So sad and uneven |
Beta Was this translation helpful? Give feedback.
-
|
The new pricing model is outright robbery!!! I've already canceled my GitHub Copilot plan subscription!! |
Beta Was this translation helpful? Give feedback.
-
|
I think it is more of a pendulum; yes, intially a lot of people will leave, but I have a feeling they will come back... eventually. |
Beta Was this translation helpful? Give feedback.
-
most likely they won't for a fairly simple reason... you have set your whole workflow on copilot, adjusted every single part to your needs and you had to, forcefully, to change to another app, another workflow, another settings and so on.... once you got used to that new one, you won't be coming back even if the older one is better just because you are tired to going back and forth... you most likely won't be doing any of this. you will stick to the new one and start adjusting yourself |
Beta Was this translation helpful? Give feedback.
-
|
I'm using VS Code with GitHub Copilot and I chose LLM GPT 5.4 Mini, but the platform is deducting the cost of Gemini 3.5 Flash, and because of that, my credits are disappearing without me using them. |
Beta Was this translation helpful? Give feedback.
-
|
I'm currently using SONET 4.6 and it's charging me for GPT 5.4 mini, are you kidding me? |
Beta Was this translation helpful? Give feedback.
-
|
@jakteixeiraf 👋🏻 Hi there, Thank you for reporting this — I want to make sure we understand what's happening. To clarify: you selected GPT 5.4 Mini in VS Code Chat, but your usage report shows charges attributed to Gemini 3.5 Flash. Is that correct? A couple of things to be aware of:
Could you please:
If the CSV confirms you're being charged for a model you didn't select for those specific interactions, please share that detail and we'll investigate further. |
Beta Was this translation helpful? Give feedback.
-
|
the admin itself is a f*****g bot :) |
Beta Was this translation helpful? Give feedback.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
-
|
How in the hell can 1 prompt which last month would barly cost a cent, now take up $4.51. this is ununsable and needs rolling back. |
Beta Was this translation helpful? Give feedback.
-
|
Yes one small UI bug fix 1,50$ lmao |
Beta Was this translation helpful? Give feedback.
-
|
Imagine , 2 calls , 550 credits so if i'm in Pro plan = 3 commands -_- |
Beta Was this translation helpful? Give feedback.
-
|
The new pricing model is outright robbery!!! I've already canceled my GitHub Copilot plan subscription!! |
Beta Was this translation helpful? Give feedback.
-
|
Check out the input/output costs for some of the agents, it's insane. Claude Sonnet is 300 input, 1500 output, 30 for cache. |
Beta Was this translation helpful? Give feedback.
-
|
So why has the Pro plan reduced its usage limit by almost 100 times compared to before? I also discovered that the |
Beta Was this translation helpful? Give feedback.
-
|
👋🏻 @SuperManito Hi there, Thank you for flagging this. Regarding the usage limit change: The billing model has shifted from counting flat requests to measuring actual token consumption (expressed as AI credits). These are different units, so a direct numerical comparison between the old request count and the new credit balance isn't apples-to-apples. Under the previous model, every request counted as "1" regardless of complexity. Under usage-based billing, a simple one-line completion costs very little, while a large multi-file generation costs more, reflecting actual compute used. Importantly:
Regarding model quality: Model behavior feedback is best surfaced through the 👍/👎 buttons on Copilot responses in VS Code - this goes directly to the team responsible for model quality. If you're seeing a consistent degradation, that feedback is valuable. For managing your usage: |
Beta Was this translation helpful? Give feedback.
-
|
You should have tested this on people instead of using AI. Most of us are willing to pay $10/month but not $100 or more per month. The mystery billing is problematic because we can use up a quarter of our budget on the 3rd and end up with nothing left by the 10th. Then we are stuck trying to decipher the zillion lines of AI generated code in order to debug problems created with the assistance of AI. I hope you will consider how this impacts your customers. |
Beta Was this translation helpful? Give feedback.
-
Brother you can't even run hundreds of thousands of tokens on a middling, non-Agentic model for $10/month. As someone who has used independent providers and hosted my own locally, frontier models are staggeringly expensive. Power users were eating up thousands and thousands of dollars in model use. |
Beta Was this translation helpful? Give feedback.
-
Except they did do that |
Beta Was this translation helpful? Give feedback.
-
You still got the year you paid for, they're just opting out of offering it going forward. I'm not trying to defend MS' actions here, just the logic behind them and how predictable it was. Have you seen what OAI or Anthropic API key rates are? |
Beta Was this translation helpful? Give feedback.
-
|
In case anyone is curious on the value comparison, this is what I am seeing on the $10 plan using GPT-5.4:
The 100 credits is an upper estimate of what I have been seeing if you assume larger prompts. I have seen as low as 10 credits and as high as 60 so far today. On average I seem to hover around 33 credits per prompt. |
Beta Was this translation helpful? Give feedback.
-
|
You're right that the units have changed: the old model counted "requests" regardless of complexity, while usage-based billing measures actual token consumption. For users who frequently use higher-cost models like GPT-5.4 with larger context, the per-interaction cost is higher than a flat request count implied. A few things that may help manage your credits:
You can see exactly what each request costs in your usage CSV: Settings → Billing and licensing → Metered usage → Copilot. For budget controls and notifications: |
Beta Was this translation helpful? Give feedback.
This comment was marked as disruptive content.
This comment was marked as disruptive content.
-
@github Community Admin And what if the output is completely useless? Users still have to pay for it—and on top of that, they then have to spend additional time fixing the mistakes in an often lengthy and expensive response. Furthermore, the creativity is completely lost, if you constantly have to monitor your token consumption and then realize, that your tokens are gone, before you even reach a viable result. You really should overthink that, otherwise you will loose a lot of customers... |
Beta Was this translation helpful? Give feedback.
-
|
Join the $10Club :) I am not going to change it at all. I just want to see where it goes. I hope they change their way of billing and continue to support the developers. |
Beta Was this translation helpful? Give feedback.
-
|
GPT-5 mini lol |
Beta Was this translation helpful? Give feedback.
-
|
In the previous thread about Usage-based Billing it seemed that a common gripe people had was that unused tokens do not roll-over into the next month. To my knowledge, the topic was never addressed by GitHub. Are GitHub able to disclose the factors contributing to this decision? While GitHub make a valid point regarding the convenience of having one bill and one set of usage controls—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. OpenRouter offers a similar set of advantages that Copilot has over other providers. It can be used within the same VS Code interface. Plus it has more models and credit rolls-over for up to a year. |
Beta Was this translation helpful? Give feedback.
-
Let them know I cancelled my office365 too because of your greed |
Beta Was this translation helpful? Give feedback.
-
|
Open Router can't change and edit files, it is useless for me, as I am not a programmer, I am a systems admin. |
Beta Was this translation helpful? Give feedback.
-
Try opencode (has a web ui and vscode plugin) with openrouter as provider. Add some specialized agents and you're off. You can even mix and match providers as you wish. Basically supports all of them since if not supported directly you can input any openAI standard API as a custom provider. |
Beta Was this translation helpful? Give feedback.
-
That may have been true some time ago. I can say with absolute certainty that using OpenRouter within VS Code is as seamless as using Copilot’s own models. If you ask Google today, the AI response will likely give you some outdated info about requiring an extension for it to work. So I understand the skepticism. Creating an account is free. Why not give it a try using one of their free models? That’s what I did last month when I was weighing out my options. |
Beta Was this translation helpful? Give feedback.
-
what do you mean? get token. connect in VSCode. all AIs that support tools connected throuhg standard VSCode can use 100% of tools there. vision, files, everything. from gemini class models to deepseek or anything, local or cloud, does not matter. as long as they speak OpenAI API. |
Beta Was this translation helpful? Give feedback.
-
|
Posting here so I can still subscribe to the chaos |
Beta Was this translation helpful? Give feedback.
-
|
I've been a paying Copilot user and this new credits system is simply unacceptable. In less than 5 hours of normal work today — the very first day of the new billing — I've already burned through 50% of my monthly plan. This is not a pricing change, this is a bait and switch. We paid for a tool, and overnight it became something we can't afford to use the way we always have. I'm canceling my subscription unless this is reverted or seriously reconsidered. |
Beta Was this translation helpful? Give feedback.
-
|
It's not just faster. It's rocket shoot... |
Beta Was this translation helpful? Give feedback.
-
|
gpt5.4 is previously 1X, now 6X. |
Beta Was this translation helpful? Give feedback.
-
|
this is fraustrating , i notice in 4 prompt of sample question it used 64% of my budget , what is going on? i tried to contact some human support of github more than 10 times, but nothing |
Beta Was this translation helpful? Give feedback.
-
|
What?? Github, but you just said to use short question, one topic per question to keep small context and now you recommended to repeat content. You mean your BIG but cached context. Great. Just continue spent money. |
Beta Was this translation helpful? Give feedback.
-
|
This looks much better Opus 4.8 - but this is not Copilot, with Copilot it would have been 2 min. on the same credits... |
Beta Was this translation helpful? Give feedback.
-
|
We are not the main target customer anymore. If you read the news, you can see that large companies are paying millions for this type of service, they don't need users like us. |
Beta Was this translation helpful? Give feedback.
-
You're right Microsoft is trusted by a lot of companies but I don't think they realize when you do customers like this they remember it |
Beta Was this translation helpful? Give feedback.
-
|
Time to ditch Microslop then and go with linux! |
Beta Was this translation helpful? Give feedback.
-
|
Well, my IT lead already looks where to limit Github Usage and try to figure out if it was a necessary usage. Actually you need good models like Opus in Enterprise context, but if time isnt crucial or you havent a customer who spends tons of money for development, I see no reason to use GitHub Copilot anymore. Its too expensive now |
Beta Was this translation helpful? Give feedback.
-
|
How many of these users are going to find out that other companies are using the same model and can be just as expensive. |
Beta Was this translation helpful? Give feedback.
-
|
Honestly, idk that will turn out to be true. We're running a comparative test after seeing this Look at the comment from OP with the screenshot... |
Beta Was this translation helpful? Give feedback.
-
It's not true he's just talking out of his bewty |
Beta Was this translation helpful? Give feedback.
-
|
not true. Deepseek is 10x cheaper |
Beta Was this translation helpful? Give feedback.
-
Yeah that guy's a moron I'm so tired of people just saying stuff |
Beta Was this translation helpful? Give feedback.
-
|
Bye-bye Copilot, if I need to pay that much I will only pay for the best tools and it is definitely not Copilot... They are just opening up their subscribers to Claude... |
Beta Was this translation helpful? Give feedback.
-
|
Well, there you have it. Big corporation bullies its customers. Business as usual, nothing to see here. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Try Cursor, it's pretty good! |
Beta Was this translation helpful? Give feedback.
-
Can I just use yours |
Beta Was this translation helpful? Give feedback.
-
|
基于 Usage-based 可以理解; 但是难以让人理解的是从请求到 premium requests 的计算方法和给每位订阅者的配给额度;
没有任何体验了, 谁会想到 github co-pilot 会用这种狠辣手段进行背刺!!! |
Beta Was this translation helpful? Give feedback.
-
|
So when can I re-apply for copilot student version? |
Beta Was this translation helpful? Give feedback.
-
|
Student Pack provides 200 credits which means its unusable now. |
Beta Was this translation helpful? Give feedback.
-
|
Where is your response to this, GitHub??? I've wasted days now looking foor alternatives to this insane price hike. As the month progresses more and more people will blast through their budgets and go looking elsewhere. Are you really going to just ghost your actual user base? |
Beta Was this translation helpful? Give feedback.
-
|
we done. |
Beta Was this translation helpful? Give feedback.
-
|
Calling paying users “abusers” feels wrong. We paid for the plan GitHub offered and used Copilot the way it was promoted. I understand unlimited usage may not be sustainable forever, but this change feels too sudden and too punishing for the users who helped prove Copilot’s value through real-world use. I hope GitHub finds a fairer balance between sustainability and the workflows people have built around Copilot. |
Beta Was this translation helpful? Give feedback.
-
Yeah these people in here saying that stuff are weirdos I've just been blocking them this threads actually been quite illuminating 😂 |
Beta Was this translation helpful? Give feedback.
-
|
Github, great job ;) |
Beta Was this translation helpful? Give feedback.
-
|
本来copilot效果比codex就差， 作为一个backup偶尔并发解决问题的。 哪里有脸像疯批一样收费， 想钱想疯了... |
Beta Was this translation helpful? Give feedback.
-
|
Title: GitHub should respond with a real adjustment to Copilot’s new pricing strategy Message: I understand that AI infrastructure is expensive, and I also understand that GitHub may need to adjust Copilot pricing as the product becomes more powerful. However, many developers have already raised serious concerns about the new usage-based pricing and AI credits system for several days now, and GitHub still has not provided a clear adjustment, compromise, or practical solution. This is very disappointing. The issue is not simply that Copilot is no longer cheap. Many of us can accept a reasonable price increase. The real problem is that the current pricing strategy feels excessive, unpredictable, and difficult to trust for daily development work. For developers using Copilot seriously in Visual Studio, Agent mode, larger repositories, refactoring tasks, and multi-file changes, credits can be consumed extremely quickly. These are exactly the scenarios where Copilot is supposed to provide the most value. But under the new pricing model, the more useful Copilot becomes, the more afraid users become to use it. That is a serious problem for a development tool. After so many users have expressed the same concerns, I expected GitHub to at least acknowledge the problem more clearly and propose some adjustments, such as increasing included credits, improving budget controls, making credit consumption more predictable, or separating normal coding assistance from heavy Agent usage. Instead, the current response feels like GitHub is simply expecting users to accept the new pricing as-is. That is not a good message to send to individual developers who have supported Copilot for a long time. I am not asking GitHub to make everything unlimited. I understand that advanced AI features have real costs. But the current pricing and credit limits feel far beyond what many individual developers can reasonably accept. Please reconsider this pricing strategy before more users lose trust in Copilot or decide to cancel their subscriptions. A reasonable price increase may be understandable. But a pricing model that feels excessive, unpredictable, and risky to use every day is not acceptable for a tool that developers are expected to rely on. |
Beta Was this translation helpful? Give feedback.
-
|
Are you sure that was not their intention to make individual users cancel their subscriptions and stop using GitHub Copilot? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, very likely Microsoft does not care about individual developers but want to focus on Enterprise customers, but this change could possibly push at least some of their Enterprise customers to their competitors... if Copilot has no more cost advantage then companies will likely pick the best tools... |
Beta Was this translation helpful? Give feedback.
-
Yes that was exactly their intention. I cancelled my Office 365 as well hopefully they realize that it cost them more than just Copilot customers and that loyalty counts for something. |
Beta Was this translation helpful? Give feedback.
-
|
I`ve used 2 days and my quota reached 99%, so I dicided to move to Antigravity and the experience is way better and cheaper than copilot. Overall, GitHub Copilot has been very helpful for increasing productivity, especially for boilerplate code, code completion, and quick prototyping. However, I am disappointed with the recent billing and quota changes. Under the previous quota model, my usage allowance would typically last almost the entire month, even with frequent daily use. Since the introduction of the new model, the same usage pattern exhausted my quota in just two days. This change significantly reduces the value of the service for heavy users and makes usage much less predictable. I would appreciate more transparent quota tracking, clearer usage estimates, and a billing model that better reflects real-world developer workflows. Additionally, the decision gives the impression that solo developers and independent professionals are not a priority. The changes seem to favor larger organizations with bigger budgets, while individual developers are left with fewer practical options. Whether intentional or not, the message many solo developers may take from this is that their needs and feedback are not being given much consideration. As someone who relies on Copilot regularly, I find that disappointing because individual developers have been an important part of the product's adoption and success. As a result, I have decided to move to Antigravity. So far, it has proven to be more transparent regarding usage and quotas, less aggressive in its billing model, and significantly more cost-effective for my workflow. I would have preferred to remain a Copilot customer, but the recent changes have made it difficult to justify the cost and predictability of the service compared to the alternatives currently available. 
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for providing detailed FAQs and improving transparency around the transition to usage-based billing. The budget controls and multi-model ecosystem are valuable additions. It would also be helpful to have more visibility into how additional usage limits are determined and clearer in-product usage analytics so users can better predict and manage their costs. Looking forward to the re-opening of sign-ups and the planned relaxation of temporary spending restrictions. |
Beta Was this translation helpful? Give feedback.
-
|
This response made me smile. Must have taken quite some time to word that with such a positive tone! 10/10, Microsoft's PR team should hire you! Haha. Because despite the positive tone you struck, the message we're all trying to portray was still accurately articulated! |
Beta Was this translation helpful? Give feedback.
-
🥒😋 |
Beta Was this translation helpful? Give feedback.
-
Microsoft's true reason for the billing change.It's no big secret that the billing for GitHub Copilot changed exactly a day before they released Microsoft Scout. A GitHub Copilot Pro subscription is a requirement to use this for AI LLM access. What is MS Scout? It's OpenClaw. Microsoft just unveiled their 'secured and business ready' wrapper and build of the most popular repo with the fastest growth on GitHub ever - OpenClaw - but instead of targeting personal users -they are targeting businesses. And it requires the AI billing of a GitHub Copilot subscription to work. Microsoft had a problem already with oversubscribed users, quotas and timeouts, this solves that. They get to upp their billing without fear of loosing users, even if they do, they will more than male that back with an influx of brand new MS Scout required subscriptions at a much higher price. And if you don't think MS Scout is going to be massive for MS, then you really don't understand the current landscape of agentic AI. This will be huge going into the future. Their blog on the release: Introducing Microsoft Scout: Your always-on personal agent | Microsoft 365 Blog https://www.microsoft.com/en-us/microsoft-365/blog/2026/06/02/introducing-microsoft-scout-your-always-on-personal-agent/ |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
All GitHub Copilot plans are now on usage-based billing
Hello GitHub Community,
Usage-based billing is now in effect for all GitHub Copilot plans. Please refer to our initial announcement and today’s changelog for more details, and you’ll find an FAQ below.
Frequently Asked Questions
Can I buy as much additional usage as I want?
After you consume your included AI Credits, you can enable additional spend by updating your budget to keep using Copilot. However, we may limit how much additional usage users on individual plans can consume based on their usage patterns, billing history, and verification states for their GitHub account. When you hit the limit, Copilot features that require additional AI credits will pause. You can either wait for the next billing cycle or upgrade to a higher plan tier to continue using Copilot. We recommend upgrading to the next plan for more included usage and higher additional usage limits.
What are the additional usage limits? How much additional usage can users purchase?
The limits increase by plan, so the limits for users on a Pro+ plan will generally be higher than those for users on a Pro plan. They also vary depending on a user’s usage patterns, billing history, and verification states for their GitHub account. These limits are subject to change, and you’ll see an in-product notification when you hit a limit.
How will we know when we hit an additional usage spending limit?
You will get an in-product notification when you hit the additional usage spending limit.
Why can’t we purchase as much additional usage as we need without upgrading to a more expensive plan?
Additional usage spending limits are a temporary measure to mitigate abuse while we observe user behavior under the new billing model. We intend to pull these back in the coming weeks, at which point you will be able to purchase additional usage without upgrading your subscription.
Why do the spending limits vary? Why are some users treated differently?
Limits vary by plan tier and account signals, including usage patterns, billing history, and verification state, to protect service reliability and prevent abuse.
How exactly are you determining the amount of a user’s additional usage spending limit? What's the specific criteria?
We look at a variety of factors, including usage and payment history with GitHub. We can’t disclose specifics, as it would give bad actors more details to work with to circumvent our safeguards.
Will we always have to upgrade to a more expensive plan when we hit an additional usage spending limit?
No, we are working on solutions for allowing users to purchase as much additional usage as they need without upgrading to a more expensive plan. That said, our subscription tiers are designed to deliver more value as they increase in cost.
If I upgrade to a more expensive plan but then decide to downgrade, what does that look like? Are there any restrictions on when I can downgrade?
You can downgrade at any point. The downgrade will be a “delayed downgrade” where you will stay in the current, more expensive plan until your next billing cycle. Then you will be charged for the downgraded plan and the lower included usage will take effect the next calendar month.
Please note that if you upgrade from a Student plan to a paid plan, downgrading will take you to a Free plan and you will need to reapply for Student plan.
You said you’d loosen restrictions once usage-based billing is in effect, but sign-ups for new users are still paused. What’s going on?
We understand the frustration. Usage-based billing is now in effect, but we’ve needed additional time to put safeguards in place to ensure a reliable experience for all users. We plan to re-enable new sign-ups for all Copilot plans in the coming weeks.
What does it look like in practice to upgrade? Can you give an example of what the flow looks like?
Once you hit an additional usage spending limit, you can upgrade to the next plan to continue using Copilot’s full set of features (code completions and next edit suggestions remain unlimited for all paid plans). By upgrading, you will be paying a prorated amount of the next plan’s cost based on your billing cycle. Your accrued additional usage will be charged during your next billing cycle.
For example, once you hit the $29 additional usage spending limit on Copilot Pro and decide to upgrade, you will pay a prorated amount of the $39 Copilot Pro+ cost and receive $70 worth of AI Credits that are currently included with the Copilot Pro+ plan. On your next billing cycle, if you stay on Copilot Pro+, you will pay the full $39 for Copilot Pro+, the $29 in additional usage from Copilot Pro, and any additional usage from Copilot Pro+. A similar experience applies from Copilot Pro+ to Copilot Max with the corresponding costs.
When can I sign up for Copilot Max?
Copilot Max is available to existing Copilot Student, Pro, and Pro+ users that would like to upgrade for more included usage. We plan to enable Copilot Max sign-ups for new users when we re-enable sign-ups for all Copilot plans in the coming weeks.
Will you continue to offer flex AI Credits after the current promotion ends?
Flex allotments may vary from month to month. They’re designed to adapt as the economics of AI evolve, including model pricing, new models, and improvements in efficiency.
Why should I pay GitHub API prices when I can just go pay the model provider directly?
Copilot gives you a single subscription across every model family we support, including OpenAI, Anthropic, Google, xAI , with model availability varying by plan— without managing separate API keys, billing relationships, or rate limits with each provider. You get one bill, one set of usage controls, and access to all of it across VS Code, the Copilot CLI, the Copilot SDK, Copilot Code Review, and tools like OpenCode — without configuring each one separately.
For a lot of developers, the value isn't just "access to a model." It's that Copilot is deeply integrated into the tools they already use: pull requests, code review, the editor, the terminal. That integration work, including the context from your repo, your PR diff, your open files, and more, is what turns a model call into something more useful.
Will users continue to see the same level of restrictive rate limiting we’ve seen over the past few months?
We’ve loosened rate limits considerably, and users should not experience them with normal use.
Can I set up budgets at the user-level for my organization?
Yes, admins can now set a universal budget for users or override for specific sets of users. As users approach their budgets, admins will receive email notifications and can adjust budgets anytime from their billing settings. See our budget management documentation for details.
Beta Was this translation helpful? Give feedback.
All reactions