Repository navigation
Single session request -> infinite premium requests consumed per tool invocation/thinking step #2591
Description
Describe the bug
Single request invocation started a session and each time agent replies as a message after tool invocation or thinking process (most probably another request made) consumes another premium requests.
So one request from me ended up consuming 80-100 requests.
Copilot CLI request estimation:
Total usage est: 1 Premium request
Affected version
GitHub Copilot CLI 1.0.21
Steps to reproduce the behavior
- Work on the project normally
- Premium requests gets consumed as the agent works through the task after each tool invocation/thinking step
Expected behavior
Usual interaction with Copilot CLI should not consume premium request per in-session process requests to server.
Additional context
- logs 1 (default level): process-1775654331415-1123.log
- logs 2 (all level): process-1775663233050-58723.public.log
- MacOS 15.7.5
- ARM
- VS Code Copilot CLI window and Warp (same consumption in both)
- zsh
- experimental feature: on
Activity
[-]Single session run consumed premium requests per tool invocation/thinking step[/-][+]Single session request -> infinite premium requests consumed per tool invocation/thinking step[/+]saa7wz commentedon Apr 8, 2026
could be related to #2568 also
rickybhullar commentedon Apr 9, 2026
This is exactly what happened to me. I was actively watching my request budget go down with every reply when I got back to my computer. Not seeing this issue on opencode @saa7wz I recommend switching to that till this is resolved.
TheBigShoe commentedon Apr 9, 2026
I am also seeing this as well. I've noticed it happens specifically with GPT5.4. About 60% of my budget was blown through in 24 hours
Ogekuri commentedon Apr 9, 2026
Same issue here.
According to this document, I am supposed to be charged for only one premium request per prompt.
Requests in GitHub Copilot:
tietoevry-johan commentedon Apr 9, 2026
Same here, seems to behave ok with Sonnet but GPT 5.3 and 5.4 are consuming like crazy despite submitting a single request
Luke220898 commentedon Apr 9, 2026
Same issue here.
PendelinP commentedon Apr 10, 2026
Same problem here—I first noticed it yesterday around noon (UTC).
jasonko7 commentedon Apr 10, 2026
Same problem here. 1.7% budget is consumed on one simple prompt with 0.33x model!
Ton-Git commentedon Apr 10, 2026
Hi, same issue here, I didn't notice it immediately and it burned 15% of my monthly quota in 2 prompts
aakjar-meyer commentedon Apr 10, 2026
Same issue here. Noticed that my last 2 prompts using Opus 4.6 consumed ~40-50 premium requests in total, when only 6 premium requests would've been used before. Following for any updates on a resolution for this.
EDIT: This is happening to me through the github.com online Copilot chat as well as the Copilot Chat within VS Code
Luke220898 commentedon Apr 10, 2026
I updated to 1.23.0 but I cannot verify if the bug is fixed because the previous version drained 100% of my premium requests.
Has anyone had their quota reset by support yet?
Ogekuri commentedon Apr 10, 2026
I'm sorry, I only have 48 credits left out of 1500 as of April 10th... 😜 the real question we should be asking ourselves is: why have a dozen of us had this problem? Are we the only ones using the Copilot CLI? 🤔🤷♂️
9 remaining items
RyanHecht commentedon Apr 13, 2026
Hi folks! We identified an issue with an experimental feature we were flighting to a small percentage of users. In some cases, it caused GPT-5-class model usage in the CLI to be overbilled.
We've since turned the feature off and are working to process refunds for affected users. If your CLI session has been open for more than a couple of days, we recommend restarting the CLI to ensure your session is no longer opted into the feature (ensuring you're on the latest
/updatewill help too!).Thank you all for your reports, they were instrumental in helping us track down the bug!
Luke220898 commentedon Apr 13, 2026
Hi @RyanHecht, thank you for the fix and the initial quota reset.
Unfortunately, I'm experiencing a strange regression and I am blocked again.
After support supposedly reset my quota today, my cli showed premium requests as "included" rather than the standard Remaining reqs 100%. I assumed the issue was fixed, but a few hours later, I was hit with the 402 You have no quota error once again.
I had already updated the CLI to 1.0.25 and completely restarted my terminal and sessions as advised.
Could you clarify if the quota resets are putting our accounts into a weird temporary state that reverts back to 0, or is it possible that a background process/local cache is still silently draining the quota despite the 1.0.25 update?
Any clarification would be greatly appreciated as I need to understand if I have to completely purge some local ~/.copilot cache before asking support for a second reset.
Ton-Git commentedon Apr 13, 2026
Hi @RyanHecht , thank you very much for the info, I had a similar issue today with my company account (copilot business): at first I was around 20% usage, then went to 0 and I saw 'included' in vscode, then it went back to the previous value.
Ogekuri commentedon Apr 13, 2026
@RyanHecht
Exactly the same for me, except I was 107% 😅
Luke220898 commentedon Apr 17, 2026
@RyanHecht It has been 4 days since my last message and my account is still completely locked with the 402 You have no quota error. Support has gone completely silent and is ignoring my tickets.
I am a paying Copilot Pro user ($10/month) who has been unable to work for days because of this bug. The initial "reset" did not work (the dashboard briefly said "included" and then died again). It is extremely frustrating to pay for a premium service, have it broken by an experimental update, and then be totally abandoned by support.
Is anyone actually looking into accounts that were broken again after the first reset, or do we all have to ask for refunds?
Luke220898 commentedon Apr 17, 2026
@RyanHecht I need to report a severe escalation of this issue.
After 1 week of completely ignoring my support tickets, an automated bot finally cancelled my Copilot Pro subscription and issued a refund.
Thinking a fresh start would fix the 402 You have no quota error, I re-subscribed and paid the $10 again (incurring bank transaction fees).
To my absolute shock, the premium quota on the renewed subscription was STILL completely empty.
The bug from v1.21.0 didn't just drain my old quota; it seems to have permanently corrupted the quota tracker for my specific GitHub account in your database.
To make matters worse, the automated system wouldn't let me auto-refund this second broken subscription.
Since human support is apparently non-existent and I have been blocked from working for 7 days, I was forced to create a completely brand-new GitHub account and pay another $10 via PayPal just to bypass your broken billing system and get back to work.
Please warn other users: do NOT try to cancel and re-subscribe on the same account to fix this bug. It does not work.
The account remains bugged. I hope a human engineer finally looks into these permanently bricked accounts.
vitalii-zelinskyi commentedon Apr 22, 2026
I’ve had the same issue in the CLI for a few weeks now. I update it every day, and I’m currently on version v1.0.34, but the problem persists. It shows a random percentage every time. In the Github UI, I saw that I had used 92% of my requests, but today, after just a few interactions with Sonnet, it showed 402. I strongly suspect that something is wrong with the counter and that it has blown up. I also highly doubt that I’ve actually consumed all my requests for this month.
nordovento commentedon Apr 23, 2026
Same here. The quota reporting is inconsistent across the GitHub UI, Android Studio, and the CLI - all three show different numbers.
In my case, the CLI returned a 402 error even though it was still showing 13% remaining.
This strongly suggests the quota counter is broken or out of sync.
RyanHecht commentedon Apr 27, 2026
Hey folks, anyone affected by the April 7-11 Copilot CLI incident will have gotten their PRU's refunded by this point!
For folks reporting other quota reporting errors, please open new issues to track those! Thanks :)
leaqigaie commentedon Apr 27, 2026
@RyanHecht
I'm in a similar situation but haven't received a refund yet. I also opened a support ticket about this two weeks ago and haven't gotten a response there either.
Luke220898 commentedon May 6, 2026
@RyanHecht
Where is my refund?