GitHub Community
GitHub Copilot is moving to usage-based billing #192948
|
Hello GitHub Community, Today we announced we are transitioning to a usage-based billing model for GitHub Copilot, effective June 1 📆 Please refer to the blog post for the full announcement link to blog, and you’ll find an FAQ below. Important June 1, 2026: Usage-based billing for GitHub Copilot is now live for all users and Copilot code review consumes GitHub Actions minutes, in addition to GitHub AI Credits. ⭐ For the most up-to-date information, we have provided more details and a FAQ in this discussion. As newer information is available, some details in this discussion may no longer be current. We closed and locked this post and recommend subscribing to the linked discussion for the latest updates and guidance. Important May 12, 2026: We've updated the body of this post to include a questions about our announcement: April reports are now available to prepare for usage-based billing 📌 Frequently Asked QuestionsWhy is GitHub changing the Copilot billing model now?We’re making this change now because GitHub Copilot simply is not the same product it was a year ago—it now powers far more complex, agentic workflows that consume far more compute. This change is designed to deliver a more sustainable and reliable product experience by aligning pricing to actual usage and costs. Isn’t this just a price increase disguised as a billing change?The per seat subscription cost of GitHub Copilot is not increasing, and code completions and Next Edit Suggestions remain unchanged. Users with intense agentic usage will likely see an increase in costs because those features consume more compute. With pooled entitlements, organizations that use Copilot Business or Copilot Enterprise may see their total charges reduced as entitlement pooling balances more active users with less active. This just wiped GitHub’s value moat – why should I stay?We believe GitHub Copilot remains the best value and experience for agentic coding. Usage-based billing aligns cost more closely to actual usage and value, while continuing to offer developers the freedom to choose the models and agents that work best for them. Will there be any free models anymore with this shift?With the shift to usage-based billing, free models are no longer part of our offering. If we run out of AI credits mid-month, does Copilot stop working?If your entitlement and set overage budget is fully consumed, you can continue to use Copilot for code completions and Next Edit Suggestions but will have to wait for your entitlements to reset, purchase additional usage, or upgrade your plan to use other features. We’ve built usage surfaces that show your consumption as a percentage of your budget and in dollar terms so you can track usage as you go and plan accordingly. For Copilot Business and Copilot Enterprise users, notification at various consumption levels will be sent to your GitHub admins as your entitlements are drawn down. With pooled entitlements, all included credits are pooled across your business. This means power users can draw more when they need it, and lighter users offset the balance. How can I forecast our AI spend if the bill changes monthly?We’re rolling out a preview bill experience in the coming weeks to show all users how their costs may shift under the new billing model. This will be available to users via their Billing Overview page when they log in to GitHub.com. We currently use PRUs for some features, how does this change that?With usage-based billing, we’re replacing PRUs with a new unit called GitHub AI Credits, which are based on the tokens your interactions consume and priced according to the listed API rates per model. All features aside from code completions and Next Edit Suggestions, which remain unlimited, will be measured and billed in GitHub AI Credits. Will Actions minutes consume my AI Credits?Your monthly bill will include both the total cost of your token usage and Actions minutes consumption. Additionally, Copilot code review recently moved to an agentic architecture that runs on GitHub Actions, and starting June 1, 2026, reviewing a pull request with Copilot will count against your included Actions minutes at the same per-minute rates as any other Actions workflow. I’m on an annual plan, how does this affect my billing?We’re retiring annual plans. If you’re currently on an annual plan, you’ll continue to use PRUs until your subscription expires. After it expires, you’ll be moved to a Copilot Free plan unless you sign up for a new monthly paid subscription. While you can keep using your annual plan until it ends, we’ll be updating model multipliers for PRUs when our new billing model goes live on June 1. We recommend switching to a usage-based monthly plan on June 1, and we’ll provide credits that reflect the prorated amount left on your annual plan subscription. How are you determining what to charge me and how does that change depending on which model I’m using?Usage-based billing means you are charged based on the tokens your interactions consume, priced according to the listed API rates per model. We’ve built usage surfaces that show your consumption as a percentage of your budget and in monetary terms. These show up in your editor, on GitHub.com, and in admin dashboards. Will you resume Copilot trials now that you’ve implemented token-based billing?Our focus has always been on lowering the barriers to entry for anyone who wants to code and that’s why we continue to offer Copilot Free as a no-cost option. Unfortunately, we’ve observed a high volume of abuse through trials and paused them while we investigate. We are actively working on improved safeguards to prevent misuse of the trial system and will share an update when we have one. Will we continue to see increased usage limiting?Unfortunately, users will continue to see increased usage limiting until usage-based billing is implemented on June 1. We know it’s frustrating, and moving to usage-based billing allows us to reduce it. By aligning usage with costs, we can provide a Copilot experience that's predictable and reliable for all users. Why not implement usage-based billing now? Why continue with painful changes like more usage limiting?Usage-based billing requires standing up a new billing and metering infrastructure, which won’t be operational until June 1. In the meantime, we need to implement additional changes to ensure a predictable, reliable experience for all users. These are short-term safeguards, and we expect to lift restrictions once our new billing model is in effect. Why are you only offering promotional pricing for existing Copilot Business and Copilot Enterprise users, and nothing for existing Pro and Pro+ users?While we're not offering promotional pricing for individual paid plans, we’re offering the same 1:1 ratio of plan price to monthly entitlements as we offer for Business and Enterprise. We believe Pro and Pro+ plans remain competitive offerings that deliver high value for individual users. Will my unused AI credits roll over from month to month?No. Your unused AI credits do not roll over from month to month. They will reset at the start of each monthly billing cycle. 🟢 Billing PreviewWhy do I have rows with 0 AIC Values?Some code reviews entries are missing AI Credit estimations. Copilot code reviews charged directly to organizations via automation or a user without a Copilot license will reflect 0 AI Credits due to a data issue. Based on the April usage report, my monthly Copilot bill is going to skyrocket. What can I do to control costs?First, be sure to set up or update your budget for additional Copilot spend today. Budgets currently set for premium request spend will automatically migrate to control AI credit spend on June 1, ensuring you stay within your intended spend. To stretch your usage, consider using lightweight models for quick questions, splitting up planning and implementation requests, and leveraging Auto Mode. Can I use the April usage report to budget for June usage?We recommend viewing the April usage report as a directional signal. It should give you a good indication of how you’ve been using Copilot and how much that type of usage will cost under usage-based billing. Please see the changelog and docs for additional information. |
Replies: 534 comments 845 replies
|
Okay, with this change, will you at least bring back Opus since we're all paying for this again? |
|
@tozorky Happened to me as well, 54% of my monthly quote gone with just one request 822 credits gone in a single request, and the project that I am working on is just a small project with few screens |
|
Codex/Antigravity's free plan is better than this paid sh*** |
|
Subject: Official Complaint: Unacceptable Billing Changes to Copilot Pro+ Plan (Account: mtaheri8541) |
|
|
My favorite part is how they refer to the free feature, that nobody bought the sub for as not changing, but the amount of work you can complete will be decimated exponentially. So it's not a price hike, but to get the same level of coding I did on the same plan last week, I need to pay around 10 times the price of the entire monthly subscription. Got it, this might seem like a cancellation but think of it more as a "total system optimization". |
|
At least bring back Opus 4.6? 4.5? |
|
Github to Pro users: Sorry sir/madam, this is only for paying customers! |
|
Hi, I already paid for Pro for an entire year, at least let me use Opus til the end of the cycle? What business decision is this? |
|
Picard and Dathon at El-Adrel! |
I highlighted the specific word that should have forewarned the users. |
|
eating more credit than a 5 worker in real life |
|
Can I request a refund for the remainder of my annual plan? I've stopped using Microsoft GitHub Copilot altogether. |
I had a dig around for this too it's in Billing & Licensing -> Licensing and then on the right you'll have your subscription and a 'Manage subscription' drop down. If you click on that you can switch to monthly billing or request a refund. Probably wait until June to do any changes or I guess you won't get any pro-rata credits. |
|
Literally why they're increasing the annual plan's premium usage request. In hope that they can screw people over hard enough that they cancel the annual plan so they stop loosing money on the old billing model. Disgusting practices |
|
I can't get in touch with anyone from support, they haven't answered tickets for over a month! REQUEST IMMEDIATE REFUND OF UNAUTHORIZED CHARGES AND DEACTIVATION OF COPILOT PRO (NON-EXISTENT ON THE PORTAL) Ticket: #4392671 |
|
Agreed. This was a bait and switch. |
|
I would like to unsubscribe github copilot, and I demand reinversement. |
|
Is there a benefit of using the Copilot Pro+ at 39$/month instead of using the Copilot Pro at 10$/month and paying for extra usage? |
|
Yes, PAYG absolutely is going to be the future, but what average user can afford $400+/month. From what I've seen there has not been an instance where a user's new monthly charge isn't going to be significantly higher. If that is the case, perhaps AI (at least CoPilot) in coding isn't a viable business model? Can you imagine a company that has 100 software engineers being told your monthly sub just went up by a factor of 10 or more? I would suspect that they would have to come up with some way to accomplish their goals with a less expensive product. This is not the first time MS has done something like this and it won't be the last. Fortunately for us users, there will be someone who will step in with a less expensive option. I'm already looking at VS Code and Gemini and will look at other options too. |
|
有的兄弟 你可能可以多使用4、5次 claude opus 4.8，但也可能更少。 |
|
they added max now you get a whole 2.9x pro+ 
|
|
So it will be gone in 7 hours of work instead of 2.5 😂only $100! |
|
how much would be the cost of the tokens? now premium request is 0.04 USD, is it going to be same or 1 million token will be around 10-20 USD and will we have any information how much token agents are using? |
|
I installed Claude Code and Codex VS Code extensions. Much better experience consumer wise. |
|
But if someone is already invested in the vscode/github copilot ecosystem, they could always use bring-your-own-model-key (BYOK) and have API pricing of the model provider directly. So even if it is a price increase, it is still quite flexible. |
You have the flexibility of paying more in every single other scenario, congrats |
|
@science64 I made github.com/PanAchy/copilot-arewecooked as a way to get a sense of what your cost will be starting June based on your historical usage. |
|
@JFlowXAI - If you think spamming the people who are on your side is the right course of action, you need to rethink. If someone was doing this to you, I suspect you would be up in arms and complaining loudly. There are ways to accomplish what you want without pissing everyone else off. Slow down, think, act rationally. |
|
tengo una suscripción Copilot Pro o Pro+ y organizacionalmente cuento con todos los servicios Microsoft Copilot 365, como aplica esto para mi. |
|
Machine translation:
@Omar5962, these changes aply to GitHub Copilot and not to Microsoft Copilot 365 services. Machine translation:
|
|
u forgot an p there in reality it is "apply" |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
I'm a bit confused by this. I currently have CoPilot Pro which gets me a set number of Premium Requests. Under the new system, that gives me US$39 a month in AI Credits. How is this different? Is this a shift to some kind of time-based system where requests that take longer cost more? What does this mean in plain language? |
|
Wow, what a bunch of greedy Fuc*ers |
|
Good Ole Claude just recommended this for me lol. Roo Code (VS Code extension — already in your VS Code marketplace) Reads files, writes files, runs terminal, chains tasks — identical to Copilot agent Cursor ($20/month flat) Windsurf ($15/month flat) |
|
Mark, we should trust your free gift aftyer you called us greedy fuc*ers? lol (jk) |
|
Regarding Roo Code (which I haven't used yet): just watch out for a (short?) potential rough time while the previous teams hands over to a new community team (link). |
I'm using cline - its good - you just have to be very organised, and set rules up. but with the addition of deepseek v4-pro you can spend ~$4-5 developing out a complex feature with a claude like model, then 80c getting deep seek to implement - If you are very brave you can ask deepseek to do it all for $1. I just implemented ~4000 lines this way, overall its okay; needs a bit of tidyup but it does work. |
|
I have a pro+ plan, I used 4.6 opus before it got removed, now trying out gpt codex 5.3. If I use let's say 90% current premium request during a month, how much would this cost me extra? Anyone know any estimates or will premium request still be included so I still get my 1500 request ? |
|
Opus 4.6 will soon cost 27x after June 1. So you'll get roughly about 140 or so requests a month of opus if my math is correct (3900 AI credits/mo. ÷ 27)? |
|
But if we pay as we go, with a large project will that not cost shit load of $$. I can use gpt 5.3 codex aswell but worried that pay as you go will cost thousands of $ vs 1500 premium request |
Yes. |
Yeah… I think folks are going to be in for a shock when the “usage cost preview” lands in May. If you’re doing agentic coding, where you set an agent on a task with a checklist or plan and then let it run for 10-15 minutes, something like 5.3-codex can easily burn through $10-15 in API credit costs, or if using 5.5 or Opus, think $30-40. Literally a single prompt could eat your entire allotment of “AI Credits”. I’m curious to see how they will handle it if a task isn’t complete. Will they do like Anthropic and stop the agent cold, just failing halfway through, or will they allow the agent to at least finish? |
不管是GPT5.4、GPT5.5、claude opus 4.7、4.8 20250601随便的4个 code agent 已经花了 53%（3707/7000）的额度，这个已经不是翻倍的问题了，感觉最少是原来的50倍消耗，这种按月用户的意义是什么（我是Pro+用户）？多么感人的体验，Github你是希望尽快把你的客户赶走吗？ |
|
Will there be changes to allow a single GitHub account to have both an Individual Pro/Pro+ subscription as well as a seat assigned by one or more Businesses or Enterprises? Or do individuals still need to create a separate GitHub account for each to prevent the wrong Business being charged, or being charged for personal use? |
|
Hi there 👋 Copilot Pro or Pro+ cannot currently be used on the same GitHub account that also has a Copilot Business or Copilot Enterprise seat assigned. For now we recommend using separate GitHub accounts to keep personal and work usage clearly separated and to help avoid any unintended billing confusion. |
|
That's not what the documentation recommends.
The whole way Copilot is billed and managed goes counter to that recommendation. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Will unused AI Credits roll over into future months or are the first $10 or $39 in AI Credits a "use it or loose it" scenario? |
It is like you expect someone with brain-defect to accept this deal. Bullshit! |
|
@nardobarbosa Are unused AI credits at least applied to other users usage? The answer to that question should be added to the FAQ. |
The linked blog post speaks about "pooling" in the context of business plans, not individual plans. The way I get that is - during the month - there's a pool of credits that can be used by many users, whether high-usage ones or low-usage ones. Not sure if that's what you're referring to. |
I was also thinking that it has been mentioned that a new billing tool will be available at the beginning of May. That should show your hypothetical spending in past months, would the usage-based billing already have been in place. |
|
Yes, this is the unfair part. In a post elsewhere, they tried to claim that this is like spotify which has a monthly cost. But there, its not a upper limit to the minutes you can listen. This is like the cell phone plans they used to have, with limited minutes without roll over. |
|
Removing the free models destroys any value in the individual plans |
|
I might just unsubscribe because of this very reason! Copilot was the only sensible package provider, but seems they want to follow in others footsteps! Maybe the change might be better, but removing free models. I am out! |
|
I was always saying that the problem with other AI is that in the middle of a project you run out of credits and don’t even get code completion. |
So what are you using today? |
|
I was relying on gpt-5 mini after the requests were depleted. I already have codex and claude subscriptions. Only kept copilot because of free models. Now I wont need copilot and will move to some other provider which provides fixed number of calls rather than token based usage. |
|
You can enable budgets on your account and keep working even after your premium requests have depleted (until you hit budget quota you set for yourself). This is how I figured that Pro+ will be more cost efficient for me based on budget I burned beyond normal Pro subscription request allowance. This is actually GREAT experience and I always felt sorry for users of other coding agents, who got overcharged beyond what they planned to spend on a single beefy prompt. |
|
What are you doing to do for GitHub student account ? About GitHub Ai Credits |
|
They have suspended the registration of Education Benefits, and I also want to know the next steps |
Please, move back into request-based billing. Thanks. |
Actually, there was Trae, which was cheaper (600 monthly requests for $7). The problem is that even those crafty lot have switched to a token-based system. Damn them |
|
It's impossible for them to move back. They used "Request-based billing" to bait you to subscribe and moved to "Token-based billing" with all the excuses their AI comes up with. |
|
Request based billing basically locks in a system where either a company is either charging way too much for tokens, or way too little. That's not a workable business model. Whether that's an excuse or a reason depends on your point of view. I think it's just a fact. |
this is true - but I found that with the extended sessions even the best models lost coherence and started developing on hallucinations - I ended up stopping them and reframing. so I'm not sure how useful is actually was |
|
Guess this is firing up https://github.com/juliusbrussee/caveman |
|
I am really sorry but I am not understanding very well the "convoluted language" you are using. I have simple questions:
|
|
If you're currently on a monthly subscription, you will be automatically be moved to usage based billing on June 1st. |
|
Why isnt there a Middle Finger Emoji? "Github Community Admin" |
|
🖕🏼 |
|
Whether this usage-based billing model is applicable only for Premium models or for all models?. |
|
|
"AI credits"?! More number games. Is there just no where for me to have anything approximating a professional coding environment now? I'm done! |
|
I hate github. |
|
What happens next month, are they rolling up the unused credits? |
|
0016 |
|
I just cancelled. What greed |
|
On my first day using this new Github feature, this is ridiculous. It would be easier to shut down the project. They shot themselves in the foot. Congratulations to everyone involved, especially @mariorod (Mario Rodriguez). Anthropic and Openai also thank you. 
|
|
The best approach for long-term AI coding workflows is probably hybrid local/cloud orchestration. High-end models like Claude Opus are extremely powerful, but they are also extremely expensive to run at scale. Hardware such as NVIDIA H100 and H200 GPUs can cost tens of thousands of dollars per unit, and large inference clusters require massive infrastructure investments. Because of that, pricing naturally reflects operational costs. Instead of using premium reasoning models for every small task, it makes more sense to use local LLMs for preprocessing and lightweight operations while reserving Opus for high-quality reasoning and generation. My suggestion is to make Copilot and GitHub Models more extensible for hybrid local/cloud AI workflows. Some ideas:
Example workflow: USER REQUEST I’m currently building something similar for my own workflow. It’s not fully complete yet, but it already helps with:
The goal is to avoid wasting expensive premium-model tokens on tasks that smaller local models can already handle efficiently. I currently run local models with 48GB of VRAM, and I’m planning to expand this further because I genuinely believe this is the future of scalable AI-assisted development. For many developers and indie studios, fully cloud-based reasoning at large scale eventually becomes too expensive. Combining smaller local models with premium hosted models can reduce token consumption significantly while still maintaining high-quality results. I think GitHub could build an incredible ecosystem around this if they made these workflows more programmable, systematic, and easier to integrate directly inside VS Code and Copilot. |
|
I knew something like this would happen, and I missed my chance to cancel it due to the stupid billing cycle Github has, I paid in May for my June subscription. It's close or even more expensive then claude code, with their stupid agent which burns even more tokens. |
|
It's like Microsoft has a historical habit of breaking everything to alienate its consumers. |
|
Do you mean GitHub going to join Nokia? |
|
Quiero dejar constancia formal de mi inconformidad con el cambio de GitHub Copilot a facturación basada en uso. |
|
Me acaba de pasar lo mismo. 1 de Junio, dos prompts y se terminaron todos los creditos de mi suscripción PRO para este mes. EN EL DIA 1. |
|
I appreciate the new higher limits for the Pro+ monthly plan, but I think GitHub should consider adding a $200+ tier above the current $100 plan with significantly higher usage limits. Right now, the $100 plan offering 2.9x usage is already a strong option, but there is still a gap for heavy professional users working daily with:
These workflows can consume tokens and context extremely quickly. Many advanced developers are already building custom systems using local Ollama models for summarization, embeddings, and repository preprocessing before sending refined context to GitHub-hosted models. A dedicated $200 premium tier focused on high-scale professional workflows would be very valuable for serious developers and indie studios. For small game studios and independent developers working daily with AI-assisted coding, a mid-tier option between Pro+ and the $200 plan would make much more sense. GitHub Copilot and GitHub Models are becoming extremely powerful, especially with models like Claude Opus. However, advanced users and indie studios are starting to hit workflow limitations that could be solved with a more modular architecture. Right now, using high-end models improperly can become extremely expensive and inefficient. Large context windows are powerful, but without proper orchestration, summarization, embeddings, and local memory handling, token usage grows too fast. My suggestion is to make Copilot and GitHub Models more extensible for hybrid local/cloud AI workflows. Some ideas:
A local model could:
Then premium models like Claude Opus could focus only on reasoning and high-quality generation instead of wasting tokens on repository scanning and repetitive context. Another important improvement would be exposing a more flexible GitHub Models API directly inside VS Code/Copilot workflows. Advanced users should be able to:
Many developers are already building custom VS Code extensions and orchestration systems to solve this problem manually. Native support from GitHub would make Copilot dramatically more scalable and efficient for professional and indie studio workflows. This becomes even more important for game development, large Unity projects, MMO architectures, and multi-language repositories where context management is one of the biggest bottlenecks. |
|
how is max a strong option at 2.9x when pro+ gone in 5hr? |
|
Mate, I use the Claude API directly, and if you don’t have a local LLM running, you can easily spend more than 10k USD just on prompt requests. That’s basic reality for large-scale projects. I bet if you put 10k USD into Claude Direct API services and worked on a big project for an entire day, you would burn through it extremely fast. It’s the same for GPT. For any serious app running with Codex/GPT 5+, I would estimate around 100 USD per day using GPT, while on Claude it can go far beyond 600 USD per day depending on the model and workload. The point is that GitHub was giving us one of the only ways to access this level of service with a much lower cost. These models always had very high pricing, and I use them daily. I can confidently say that if you use Opus 4+ directly through the Claude API, you can easily spend over 200 USD per day. If you move to something like Opus 4.6, it can hit 600 USD per day or even more with 8–10 hours of active development work. That’s why I kept asking myself how GitHub was managing to offer this, because I buy server infrastructure and AI services directly, and the operational costs are always extremely expensive. Like I said, around 600 USD per day with Claude Opus 4.6 working heavily for 8–10 hours, and around 100 USD per day using GPT 5.3 Codex. I’ve managed to reduce these costs by configuring a local Ollama setup and using 2x P40 GPUs to run local agent skills and other workloads locally instead of relying entirely on external APIs. |
|
that not the issue, the issue we know there costs. the issue i use many services. i come to copilot 1.5 years ago and they offer service which they offer and they run for years. they know day 1 if the service is sustainable or it takes years? they know day 1 and yet they run it and run it for charity? no they run it to get user into their service and then pull rug and price x100 ion one day, that is issue, |
|
I cancelled my Copilot Pro suscription and I even got a reinbursement on that they. But when my usual cut-off date came again (may 22nd) I received a new charge. I rose a support tocket with no reply since then. support@github.com bounces my messages. How can I get my money back and make sure it doesn't happen anymore. |
|
Haha, get token'ed, slopcoders |
|
and what are you a pro claude master, |
|
I write code, without LLMs. What an outlandish concept that must be to people in 2026. |
|
After using Copilot Pro+ in real daily development, I’m seeing a clear mismatch between included AI credits and actual workflow usage. |
|
This pricing change is a precise double strike. |
|
are github copilot guys crazy? my 12% of total ai credits burned like anything for very minor task. I used Claude Sonnet 4.6 as usual and in response it barely updated 2-3 lines in total 6 files which costed like ~$0.35 per line updates. 
|
|
Work with other extensions that can use Alibaba, DeepSeek, Moonshot, and/or Tencent. It's good to have access to Gemini too unless they too decide to go greed with pricing. Your flow will be restored and they each have top models that are extremely capable with fair pricing. |
🆕 Community Manager Update: June 1, 2026Hello everyone, Usage-based billing for GitHub Copilot is now live for all users and Copilot code review consumes GitHub Actions minutes, in addition to GitHub AI Credits. As part of this release, we're also launching new user-level budget controls, expanded context windows, and enabling upgrades to Copilot Max. ⭐ For the most up-to-date information, we have provided more details and a FAQ in this discussion. As newer information is available, some details in this discussion may no longer be current. We'll be closing this post and recommend subscribing to the linked discussion for the latest updates and guidance. |
|
In a fresh project, I replaced the 'forgot password' email verification code with a direct reset link. This change cost me 270 AI tokens—or about 18% of limit on Copilot Pro. I have no idea why the AI agent then suggested applying the same style to other pages, especially since that was already done. It ended up charging more AI tokens for absolutely zero code changes. |
|
create a cancel page save everyone looking |
|
Copilot pulled off a masterclass: they forced millions of satisfied users, who wouldn't even think to look for something cheaper or better, to search for alternatives to their flagship product. If they wanted to slash the number of active users, that's just a brilliant chess move – unless they have an inside mole who came up with this 'genius' idea. ;) - On a side note: 60% of my current Pro+ plan is gone with the wind—before this, the same daily workload used to consume just 3-5% (gpt 5.4) |
|
The strategy is clear, but it would have been good to say from the beginning, "This is a subsidized trial" or something similar, to promote our tool. Since they already have millions of users, they're now going to keep 5% by paying $100 USD. The rest of us have to create our own tool to go directly to OpenAI, Claude, or Gemini API's or Antigravity. |
|
"But I thought the free sample platter was infinite and lasted forever, that's why I taught myself how to forget how to cook or use a microwave!" |
|
The golden age is just beginning. Switch to Alibaba's plans and use it with another extension. Or to Moonshot. Or to DeepSeek. or to Tencent... or to any of them. The greed is very clear, which few are trying to "Phoebus Cartel" AI and which others are ignoring them while delivering to the World anyway. |
|
did anyoine say it was a sample platter? |
|
Hello, As of June 1, 2026: Usage-based billing for GitHub Copilot is now live for all users and Copilot code review consumes GitHub Actions minutes, in addition to GitHub AI Credits. As part of this release, we're also launching new user-level budget controls, expanded context windows, and enabling upgrades to Copilot Max. ⭐ For the most up-to-date information, we have provided more details and a FAQ in this discussion. As newer information is available, some details in this discussion may no longer be current. We'll be closing and locking this post and recommend subscribing to the linked discussion for the latest updates and guidance. |
and others
🆕 Community Manager Update: June 1, 2026
Hello everyone,
Usage-based billing for GitHub Copilot is now live for all users and Copilot code review consumes GitHub Actions minutes, in addition to GitHub AI Credits.
As part of this release, we're also launching new user-level budget controls, expanded context windows, and enabling upgrades to Copilot Max.
⭐ For the most up-to-date information, we have provided more details and a FAQ in this discussion.
As newer information is available, some details in this discussion may no longer be current. We'll be closing this post and recommend subscribing to the linked discussion for the latest updates and guidance.