GitHub Copilot AI Credits Are Unfair, Expensive, and Killing Real Development Workflows #198015
Replies: 80 comments 66 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
We no longer are able to choose a free agent after using our credits. It used to select one automatically if you chose. This has gotten to be outrageous |
Beta Was this translation helpful? Give feedback.
-
|
They will never see me again until they change their plans again |
Beta Was this translation helpful? Give feedback.
-
|
I completely agree with this and really hope GitHub listens to the feedback from the community. |
Beta Was this translation helpful? Give feedback.
-
|
Sigh, you're all wrong. This is a business decision. Just look at the community feedback to see that—there won't be any more subsidies, and they won't come back. |
Beta Was this translation helpful? Give feedback.
-
|
I completely agree with @KarimWajihKMW. I find myself constantly checking my billing settings page https://github.com/settings/billing/ai_usage just to monitor usage and figure out how the system calculates it. Hopefully, GitHub improves this very soon. |
Beta Was this translation helpful? Give feedback.
-
|
We have provided more details and a FAQ about usage-based billing in this discussion, which may be updated if new information becomes available. To keep conversations all in one place and to ensure you receive timely updates, we’ll be closing this post and recommend you comment on or subscribe to the discussion linked above. |
Beta Was this translation helpful? Give feedback.
-
|
sams for. me , some how 52% of my monthly tokens are used justed in one day (2 of july 2026) ,while it used to fit for the whole month, i am very disappointed and actively searching for alternatives. |
Beta Was this translation helpful? Give feedback.
-
|
Same, even I have dropped the individual plan and even at my office i have told that we need to move, this is killing productivity, even $70 is worse than claude code $20 plan, and claude code was in it self less. This is really frustrating as a user, subpar vibe coding experinace (when compared to codex or claude or even open code) and credits vanish like anything. |
Beta Was this translation helpful? Give feedback.
-
|
I moved to codex, cool pilot is useless with this pricing |
Beta Was this translation helpful? Give feedback.
-
|
The primary issue for me using this via vscode is that its not even using (on auto mode) the better AI and even if it was im paying for its mistakes. At this price and pace i am burning through my tokens too fast to be of value or use. Mostly spinning fixing its mistakes. This is not a useful product, I am switching to other vendors. 1/1000th of my tokens for running a script One day resulted in 30% token use, it results in anxiety in using AI. As others said, before i ask to perform a task i have no idea what the cost will be or if i can complete a task in budget. Given the AI generates quite unreadable code in many cases, or code that needs AI to fix due to its sloppy design or volumous generation - its no longer valuable to me at these prices. |
Beta Was this translation helpful? Give feedback.
-
|
I think the community needs two things very clearly from GitHub Copilot's new AI Credits model: 1. Credit Preview Before Execution Before any prompt is executed, users should be able to see an estimated credit/token cost. Similar to how cloud providers show estimated costs before running resources, Copilot should display a credit preview so developers can make informed decisions before consuming credits. 2. Fair Credit Refunds for Unsuccessful Agentic Tasks If an agentic task does not achieve the requested outcome and the user ultimately reverts or discards all generated changes, there should be a mechanism to refund credits or provide credit compensation. Users should not be charged the full cost when the generated result is unusable and requires complete rollback. The current model lacks transparency and puts too much risk on the user. Better cost visibility and a fair refund policy would significantly improve trust in Copilot and encourage adoption of advanced features. Jitendra Pal | Principal QA |
Beta Was this translation helpful? Give feedback.
-
|
Congratulations on launching one of the WORST plans ever. Thanks for helping us to make a decision on which platform we have to switch. 👎👎👎👎👎 |
Beta Was this translation helpful? Give feedback.
-
|
Very worst experience with these plans
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Vaibhav Nagariya ***@***.***>
Sent: Saturday, 06 June 2026 10:59:15
To: community/community ***@***.***>
Cc: Rajasekhar ***@***.***>; Comment ***@***.***>
Subject: Re: [community/community] GitHub Copilot AI Credits Are Unfair, Expensive, and Killing Real Development Workflows (Discussion #198015)
I had a similar experience. I don't use copilot for heavy coding task on large repo. I use it for normal edits in bulk, scripting, automation etc.
With just 10$ flat fee I never had to pay more earlier. This month I consumed all my credits within few hours that too for a very light weight task.
I had to cancel my subscription and move to another solution.
Very disappointed by this change.
—
Reply to this email directly, view it on GitHub<#198015?email_source=notifications&email_token=AE3PRFFELOY3X2XGNIFLL2D46OT2VA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGAYDANJXUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17200057>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AE3PRFBENEYSFWTB32A3PMT46OT2VAVCNFSM6AAAAACZ2M72V2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMRQGAYDKNY>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I was skeptical of the all the nay slayers. I even upgraded to the MAX plan because I assumed having the 20k credits would be plenty. WOW was I wrong. I burned through it in a matter of HOURS. Yes, I use Opus 4.8 in XHigh and I can switch to lower models. But it seems like we're stuck choosing to spend more time on getting worse results vs getting better results quicker. I'll play around with other models and reasoning effort but so far...yikes. |
Beta Was this translation helpful? Give feedback.
-
|
GitHub Copilot Pro used to get me through the month. Now 10 minutes took 95% of my quota... Thats how companies die, you know... |
Beta Was this translation helpful? Give feedback.
-
|
Microslop greeddddd |
Beta Was this translation helpful? Give feedback.
-
|
Try using Pi.dev I realize it isn't VSCode although some alternative has to
exist with a similar philosophy to Pi. But you won't get that junked up
context with Pi unless you decide to do it that way yourself.
Soli Deo Gloria,
Jeremy C. Morris
…On Sat, Jun 20, 2026, 12:32 PM Carson C. ***@***.***> wrote:
I use VSCode and I honestly think this is a huge failure of the VSCode's
implementation of Agent mode. GHCopilot has to change their billing because
a horribly implemented Agent mode is likely costing them fountains of money.
I ran out of credits so I added a Gemini API Key and enabled Logging to
see the input that Copilot was passing to the API. In Agent mode there is a
totally impressive waste of input tokens that drives up the cost to use the
model. Input tokens are cheap, often a quarter or less the price of an
Output token. However, this fact is irrelevant when VSCode spams the Input
with useless tokens. From my tests, on average and depending on the chosen
model, the Input tokens per request is roughly 60x the amount of output
tokens per request. This was under a relatively simple task.
The problem is the agents' carefree use of tools spamming and filling up
the input tokens with every useless file the agent decides to crawl, even
if you've given the agent all files it should need to perform the task.
With every tool call, a new request is made to the API and the past output
from the model gets fed to the input causing the input to grow
exponentially. For example, a frontier model such as Gemini 3.5 Flash,
given a simple task and roughly 3,000 token starting prompt was quickly
rate limited after accrewing 2.4 million input tokens after only two
minutes. In the same time, the model outputted 40,000 Output tokens. By the
tenth tool call the model made, each request made to the API was roughly
200,000 input tokens. Using a more capable model means fewer wasted tools
but a higher cost.
VSCode team simply needs to think about how they utilize Input tokens and
how models actually interact with tools.
—
Reply to this email directly, view it on GitHub
<#198015?email_source=notifications&email_token=ABFS56PBNAJ676NDDZTPGID5A3DBZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZTG42TSNJUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17375954>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABFS56KOURAKYZDBU6WVQJD5A3DBZAVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMBRHE4DAOBSUF3AE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Microsoft Team, the credit system has to change. I echo everyone who has written a message in this thread. I have the Copilot Pro+ plan and notice the credits are exhausted extremely fast - only 5 days of work. Before, Copilot Pro+ was enough for a month's work. I have completely moved on to Claude Code and stopped using Copilot. How am I able to do my daily work with Claude Clode on a Claude Pro subscription ($300 yearly)? And that includes Claude.ai, Cowork and Design. I understand that AI compute is expensive and the previous requests usage model wasn't cost effective but you have gone from one extreme to the other. Instead, why not offer discounted access to students instead of completely free (with certain amoung of free credits). Change the credit system somehow so that we get more usage out of it because currently it's unsusable. Keep the same models in all paid plans. You are loosing consumer trust and clearly loosing revenue from canceled subscriptions instead of computed tokens. It was a bad move to remove the Opus 4.6 models from the Pro plans. The credit system is the straw that broke the camel's back. I hope there will be changes to the Copilot credit system in the future |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Root cause is Microsoft's inability to make deal with Atrophic, and we customers pay that price. What Eventually what you get dear MS team, that majority of developers will go directly to suppliers and literally no once will use Copilot. |
Beta Was this translation helpful? Give feedback.
-
|
hehe, noobs |
Beta Was this translation helpful? Give feedback.
-
|
After the update my normal request burned through 85% of my tokens in few hours, like wtf i haven't been able to use what i paid for. I just cancelled the plan and prolly switch to something that's worth the money. |
Beta Was this translation helpful? Give feedback.
-
|
Uber was dirt cheap when it needed to hoard market share. With time passing, they needed to get profitable after the losses made to gain market. It is just how it goes, and Copilot isn't different. For a while we will be able to use other providers' agents for cheap, but eventually we will choose to either walk (fall back to manual programming) or be prepared to pay a lot for a taxi (pay 300$/month if not more in tokens). Another option is buying a car (hosting a local agent), knowing that with one's budget (for hardware and open source models) it won't be as comfortable as an Uber ride as you will also have to drive it yourself (host it). |
Beta Was this translation helpful? Give feedback.
-
This is ridiculous. I asked Copilot to just make a SMALL plan, but it started doing... I don't know how to call it
|
Beta Was this translation helpful? Give feedback.
-
|
shiiiit i think that i only people that have this problem! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
so i think we must be switch to another agents |
Beta Was this translation helpful? Give feedback.
-
|
the challenge seems to be that the copilot agent harness is super inefficient with tokens, and even with a more efficient harness and just using the copilot keys, caching seems to be limited or completely not used. when testing with opencode or pi or Zed harness, no cache tokens are reported at all. when using the copilot harness with logging on, input tokens balloon with each new query. even cheap models burn through context window MUCH faster using the copilot harness than using other harnesses, but cache is something on the server side, not on the harness side, so that's 100% on Microsoft to sort through. Certainly people shouldn't expect tons of usage on a model like Opus 4.8, but when you can pay the listed per-token fees for using Opus on other servers (OpenRouter, OpenCode, Google Vertex from our tests) and Copilot is burning 10-20x the tokens, the problem is with the harness. Cheaper models like 3.1 Flash or Sonnet 4.6 are also using significantly more tokens than they do on any other harness. |
Beta Was this translation helpful? Give feedback.




Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Copilot in GitHub
Body
I am very disappointed with the new GitHub Copilot AI Credits pricing model.
Since the June 1 update, Copilot has become unpredictable and much more expensive. Credits are consumed too quickly, especially when using agent mode, code review, debugging, or repository-related tasks.
The biggest problem is that users cannot clearly know how much a task will cost before running it. One task can burn a large amount of credits without enough warning or transparency.
This is unfair for developers, freelancers, and small businesses who trusted Copilot as an affordable coding assistant.
I used 100% of copilot pro+ in just 2 days of normal work which I used to do months and years ago.
GitHub should seriously reconsider this pricing model, increase the included credits, add clear cost warnings before each task, and give users better control over credit spending.
The current system makes Copilot feel risky to use instead of helpful.
Beta Was this translation helpful? Give feedback.
All reactions