GitHub Community
Obscenely Long Rate Limits (Over 24 Hours) and Possible Distillation False Positive #192435
Replies: 48 comments 131 replies
-
|
66 hours!!!!! paying enterprise prices for a single person on copilot pro+ you all are F*ing insane!! |
Beta Was this translation helpful? Give feedback.
-
|
make syou wonder what teh actaul rate you get is...for the week.... |
Beta Was this translation helpful? Give feedback.
-
|
Have you opened a ticket with support? I've just opened one. Hopefully this'll be fixed and I can get some work done tomorrow. |
Beta Was this translation helpful? Give feedback.
-
|
yeah i did. |
Beta Was this translation helpful? Give feedback.
-
|
auto mode seems to work but who knows how long that will last and again when you're paying, being forced to use it is crazy. |
Beta Was this translation helpful? Give feedback.
-
|
Estou com o mesmo problema. caso não haja solução, que ferramenta pode substituir o vscode e copilot? como ter uma segunda alternativa? |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same issue ^ |
Beta Was this translation helpful? Give feedback.
-
|
Same issue happened to me. It’s due to rate limiting. |
Beta Was this translation helpful? Give feedback.
-
|
"Not a bug" no, deliberate action they admitted to and a "contributor" just reiterated. |
Beta Was this translation helpful? Give feedback.
-
|
No solution as of yet. Resorted to auto mode and am getting sub-par code quality. |
Beta Was this translation helpful? Give feedback.
-
|
yeah and even worse than that i had one system that couldn't use anything but gpt, so i'm using antigravity to sort it out and see if i can get it to use auto afer fixing the extension; i digress, i guess i'll be finding a suitable intermediary and limiting my github usage at this point. they definitely got greedy overnight with that and i know folks are making a killing off the api's for this. i have 22llm's i'm bound to break one free for my own copilot. |
Beta Was this translation helpful? Give feedback.
-
|
no way i'm paying over $100 to get this kind of nonsense. |
Beta Was this translation helpful? Give feedback.
-
Insult to injury...why is teh cli even longer? yeah i definitely need to make better moves now. now auto for the cli either.
|
Beta Was this translation helpful? Give feedback.
-
|
Perhaps related? |
Beta Was this translation helpful? Give feedback.
-
|
anthropic was already taxing them from what i read so this makes sense, but as you said, we get punished for cashing out...which is crazy. What's even worse is the "upgrade your plan". Uh, you only have pro+ for regular users...we can't go any higher and this crap here is not how you get folks to look into your plans when you have so many separate payment situations for everything already. and again, there's the overbudget feature that is now completely useless with this change. |
Beta Was this translation helpful? Give feedback.
-
Of course I have, that's why I'm paying you (GitHub) to get rid of the limits. I won't pay more to increase my "weekly rate limits" as well if I'm just a hobbyist who's ALREADY SUBSCRIBING, so that's not my problem and I don't care how, but solve it. And if you want to punish people for wanting to do something - while you yourself are being greedy - then... maybe it's time to say good bye to any cash that was going to you, and use a local LLM instead? |
Beta Was this translation helpful? Give feedback.
-
|
不知道有什么办法可以解决？ |
Beta Was this translation helpful? Give feedback.
-
|
you would be wasting your money and making this a legit reason for them to keep going. don't give them any more money if you are already on a pro+ account...you literally can't go any higher or change teh rate limits regardless. 你这样做只会浪费钱，而且会让他们以此为借口继续骚扰你。如果你已经是专业版+账户，就别再给他们钱了……无论如何，你都无法升级到更高等级或更改费率限制。 |
Beta Was this translation helpful? Give feedback.
-
|
lol, if you are on a pro account...go ahead...that might give you an extra day. |
Beta Was this translation helpful? Give feedback.
-
No, I enountered this in my Pro+ subscriptions, so there is no way. |
Beta Was this translation helpful? Give feedback.
-
|
Has anybody had any responses to any support tickets yet? |
Beta Was this translation helpful? Give feedback.
-
|
This outcome was exactly what I expected: GitHub’s level of subsidization appears to have reached a point that is no longer sustainable. As a result, this feels less like a bug and more like a business decision. I’m also skeptical that a request-based commercial model will remain viable in the long run. It’s surprising how many tokens can be consumed in a single conversation turn, and it seems they ultimately chose to shut this down. Still, enforcing both a turn-based request limit and a usage-based request limit at the same time is not user-friendly. I wish they would switch entirely to usage-based limits and provide a visible gauge, rather than locking users out for hours. |
Beta Was this translation helpful? Give feedback.
-
|
The 1500 premium request for Pro+ users has become a joke since this change; they are now blocking users based on whatever non-transparent internal AI-slop logic they use. |
Beta Was this translation helpful? Give feedback.
-
exactly, they suck. |
Beta Was this translation helpful? Give feedback.
-
|
They need to do what cell companies had to do with unlimited data and just give us slower TPS or find another way to degrade the service without it completely breaking our workflow. Doesn't help that everyone resets at the same time meaning servers get slammed harder on the first of the month, seems like they are making it harder on themselves. What burns the bridge is hiding the Rate limit metric, no reason we shouldn't have a progress bar right now to know when were getting close so we can walk away and take a break for an hour. Lastly the message saying "Reset" at this time is misleading... We know its like a charged ultimate and it just outputs the time where it'll let you request something not that it can actually do anything as you'll just get rate limited again, at least give the true reset time. |
Beta Was this translation helpful? Give feedback.
-
|
"you’ll need to wait until your session resets. The reset timing should be indicated in the error message when the rate limit is reached." They act like the service becomes usable if you wait til that time like it's an actual reset.... how disconnected can support be. |
Beta Was this translation helpful? Give feedback.
-
Why is GPT 4.1 rate limited too? I can't use any models. This is crazy. I'm on Pro+ |
Beta Was this translation helpful? Give feedback.
-
|
It seems that the rule might be that when you hit a rate limit, all options for model selection are inaccessible, leaving only |
Beta Was this translation helpful? Give feedback.
-
|
The fact that auto is still available makes me suspicious that this is an attempt to curb attempted use of Copilot for specific model distillation. |
Beta Was this translation helpful? Give feedback.
-
|
I said the same thing, the only other options were Grok and Gemini (or lesser gpt's)...so what is happening exactly!?! are they using lesser reasoning on the models and swapping between them on the fly during conversations? If so, them my 22llm setup is bound to become more useful if I can do that myself. So far its only got governance and memory down I can't figure out the tool calling and fluid conversation just yet. |
Beta Was this translation helpful? Give feedback.
-
|
Yep , looks like rate limit is on account level, not per-model basis. Some data and information inside the dashboard to understand this better would be great. People use it for work, so having clarity is very important in my opinion. From work tool, it might become a toy like many other products in the space. |
Beta Was this translation helpful? Give feedback.
-
|
If this keeps up, I'm literally not renewing next month. |
Beta Was this translation helpful? Give feedback.
-
|
It appears that this won't be rectified, so where next? What other services offer similar pricing but actually let us pay and use the service? |
Beta Was this translation helpful? Give feedback.
-
|
I don't think such a service exists anymore; almost all the AI harness providers have switched to usage-based rate limiting, Anthropic, Codex, Cursor, etc. |
Beta Was this translation helpful? Give feedback.
-
|
Perhaps the only thing we can do is wait for the infrastructure to perfect globally. |
Beta Was this translation helpful? Give feedback.
-
|
Does hugging face offer these kinds of services? |
Beta Was this translation helpful? Give feedback.
-
|
I think they do but I cannot speak to the quality. Perhaps it would be worth cancelling Copilot and saving the money for a while until you can buy used GPUs? Then you can run some decent local models (which are getting better all the time). |
Beta Was this translation helpful? Give feedback.
-
|
I'm super close. I already have open claw activated and setup for what i have going on and i just discovered in need to actuallly create subagents but I already have 80 that are now reactivated properly with python and rust. i just found the ollama extension and set that up...so maybe the timing wasn't bad at all. i'll just abuse the auto since it hasn't stopped yet and i have my steamdeck and main system buzzing. |
Beta Was this translation helpful? Give feedback.
-
|
Server Error: Sorry, you've exceeded your weekly rate limit. Please review our Terms of Service. Error Code: user_weekly_rate_limited Its just Tuesday! |
Beta Was this translation helpful? Give feedback.
-
|
I canceled my Pro+ subscription beacause of this 33 hours limited WTF!! |
Beta Was this translation helpful? Give feedback.
-
|
lol, one of my session said 110 |
Beta Was this translation helpful? Give feedback.
-
So they're definitely switching between those "rate'limited" models fyi. |
Beta Was this translation helpful? Give feedback.
-
|
Last night, the Auto was routing me to GPT 5.3-Codex, and now it's routing me to GPT 5.4. I'm not sure what the internal logic is for Auto. 
|
Beta Was this translation helpful? Give feedback.
-
|
Smells like an LLM is doing the classification job. 
|
Beta Was this translation helpful? Give feedback.
-
|
It tries to use Claude as a sub agent and switches between gpt and Claude still, lowest being 5.3 so I agree. They're leaning and they don't want to admit it or pay up because from all the responses, folks are getting shorted prematurely too. I usually have at least 4 systems with several session running so I expect it but not this harsh. Auto coupled with what I already created seems to sustain somewhat but yeah...they're definitely about lose customers...I think ill just wait until they actually try to charge me before I decide...I could just run it up until they actually close the account. |
Beta Was this translation helpful? Give feedback.
-
|
Also hit the weekly limit after 1 day, but nothing is working in VS chat, auto or specific model - just hangs on the three dots. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah that happens when I use android studio. I have one system also that can't use anything but gpt (still can't figure out why) so that one's basically useless unless I use anti gravity or my Claude subscription. |
Beta Was this translation helpful? Give feedback.
-
|
I also encountered this problem. I encountered a rate limit when subscribing to Pro before, so I upgraded to Pro+. However, today while continuing to work on the project, I was directly informed Sorry, you've hit a rate limit that restricts the number of Copilot model requests you can make within a specific time period. Please try again on Apr 20 at 8 AM. Please review our Terms of Service ( https://docs.github.com/site-policy/github-terms/github-terms-of-service ). (Request ID: 84B2:2B0EDA: 150FC41:17B234F: 69DF48DD). Now only the "auto" mode is available, but I only used less than 20% of the credit limit |
Beta Was this translation helpful? Give feedback.
-
|
GitHub are still completely silent on the rate limiting issue. Why are they adding new models from upstream providers (like Opus 4.7) while most of their subscribers are barred from using them? |
Beta Was this translation helpful? Give feedback.
-
|
Not to mention they just added a day to my rate-limit. Lol |
Beta Was this translation helpful? Give feedback.
-
Because it's a good excuse for them to switch from the 3x to the 7.5x (likely 15x after the discount ends) multiplier, this is effectively a price increase. If you check the model price from the open router, it's not hard to see that all three Opuses are priced the same at the API level, and obviously, providers don't subsidize APIs. 
|
Beta Was this translation helpful? Give feedback.
-
|
Now I just keep getting told to wait 4-14 minutes every time I send an Opus 4.6 request. I wait double that time, send a request, then get another 4-14 minute rate limit. |
Beta Was this translation helpful? Give feedback.
-
|
Yep, its crazy and ridiculous. It used to show the actual time you were limited for, now just tells you to try again after waiting 5 mins and its just none stop. |
Beta Was this translation helpful? Give feedback.
-
Sounds like an excellent strategy to prevent users from creating a stunning screenshot. (Or delay them from getting to this discussion thread too early). |
Beta Was this translation helpful? Give feedback.
-
|
Yep, exactly |
Beta Was this translation helpful? Give feedback.
-
|
One long rate limit can be difficult and frustrating but this is just a permanent bar from the service now. Perhaps it would be worth it to reach out to tech news sites and blogs? |
Beta Was this translation helpful? Give feedback.
-
|
Mine as never consistent when they were giving the actual hours either. |
Beta Was this translation helpful? Give feedback.
-
I think the issue is that you had multiple windows of your code running, i had 5 open and i was making the other 4 projects implement what I had done in the 5 project, after a few mins i got hit with weekly rate limit and to check their tos, I then went to vs code and tried there and it gave me a more transparent time....... 196 hrs(even though it stated a WEEKLY rate limit). To me it seems like im soft banned from using for 196 hours...... After reviewing their TOS some more, I noticed a part about "bot acccounts". Thats the ONLY thing I think it could be since from their systems prospective it could be flagged as that since I had all those instances running implementing my other projects logic and code. I think this is ridiculous and will be canceling my subscription and not spending another dollar unless they revert it back to how it was before! Ive never been limited like that, run out of request or whatever sure, but i would just add a another 100-150 budget in and be fine, most months I never even hit my mothly subscription, at this rate I wont even hit 20%! No point in having the most expensive plan anymore or a plan at all anymore on here. |
Beta Was this translation helpful? Give feedback.
-
Not entirely sure what In my use case, my entire conversation can easily go past 1M tokens without tool call results (excluding file contents), assuming their cache read is 0$, you still need to count |
Beta Was this translation helpful? Give feedback.
-
|
I don't know much so im learning but tool calling is only done server side? Basically I've been building my own version of a copilot because windows version sucks and github has what I need, lol. Anyway, my point being, if I already have locally, what the copilot would look for "intelligently" via whatever protocols and tool-calling goes on there....wouldn't I in essence be avoiding the need for excessive token usage? Again, I don't know much so no need to assume I do. |
Beta Was this translation helpful? Give feedback.
-
|
I also see that I truly don't understand the cache topic. |
Beta Was this translation helpful? Give feedback.
-
Here is an explanatory video about LLM harneses (or "Copilot"), which I think may be beneficial to you, as it seems that you are creating your own version of Copilot. How does Claude Code actually work? In summary, a The entire context, which includes all history since the conversation began—such as the system prompt and all previous exchanges—remains intact, plus the tool call results you appended. This updated context is then sent back to the LLM's API endpoint, the part that's intact, triggering caching (billed as cached inputs), with the newly appended results of the tool call (billed as input tokens). The LLM continues generating the next segment of text (billed as output tokens), and the process repeats until the LLM decides to generate an |
Beta Was this translation helpful? Give feedback.
-
|
Thank you but that still brings me to my point, my token usage has solely been agentic work (which it seems theyre targeting and the harnesses) but as of late it hasn't been anything but light work (to me) with me already having most of it built...according to copilot, lol. So what if I was just asking questions and not calling tools at all? I digress, I figured a lot of it was done on their servers so I was just curious if we could circumvent and eliminate the heavy usage there. Guess not. I have openclaw and most of the scripting and stuff done but im still having trouble getting the streaming to stick and actually call the tools. But the conversations happen somewhat when I don't break my server. |
Beta Was this translation helpful? Give feedback.
-
|
Tried Opus 4.6 again, now it just says "Working" and never does anything. Are they trying to make the rate limits more discreet? Is anybody else experiencing this? |
Beta Was this translation helpful? Give feedback.
-
Yes they are. They had my rate limit time ONLY on vs code (not community), I checked to day the hours left and it just kept saying try again every few minuets never giving me my total time |
Beta Was this translation helpful? Give feedback.
-
|
Do you think it's related to this also? |
Beta Was this translation helpful? Give feedback.
-
|
@eimkasp That tweet comes 2 days after I was hit with the initial 44 hour rate limit and relates to 4.7, whilst I was attempting to use 4.6 |
Beta Was this translation helpful? Give feedback.
-
|
I've been able to send a single Opus 4.6 request. It took a while to respond but I no longer seem to be rate limited. I suggest everybody try again now and we can see if it is truly fixed or if we're just in the "eye of the storm" so to speak. If this is over (and it may not be for everyone), why was this allowed to happen and why wasn't it acknowledged by GitHub? My support ticket still has no response. |
Beta Was this translation helpful? Give feedback.
-
|
As I expected. I'll keep posting here checking in. I'm still not satisfied with the way GitHub is handling this, despite the fact the problem seems (perhaps temporarily) alleviated for me. The silence alone is enough to make me consider an alternative service. |
Beta Was this translation helpful? Give feedback.
-
|
You've reached your weekly rate limit. Please upgrade your plan or wait for your limit to reset on 2026年4月20日 8:00. me too |
Beta Was this translation helpful? Give feedback.
-
|
Lol, they just added 3 days. Auto has been working, albeit sketchy and failing in some instances but enough to get maybe 1 or 2 complete coding segments done...if I could say that. Definitely inconsistent though and only works on 3 of 4 of my machines which is something I can't figure out for someone reason. |
Beta Was this translation helpful? Give feedback.
-
|
It reset and then I literally used it for an hour, no subagents and then I got a weekly limit resetting on the 20th! Wth! 
|
Beta Was this translation helpful? Give feedback.
-
|
@sgaabdu4 @wzh5550123 haha funny, exactly the same. started working today, used it a bit, legitimate usage using autopilot and continuing after copilot cli finishes. ironically exactly the 20th for me too |
Beta Was this translation helpful? Give feedback.
-
|
This throttling is literally brain-dead. Tasks I could one-shot with Opus 4.6 now take GPT 5.3 Codex like ten tries, and it still misses the mark. Like, what’s the point besides wasting my time and burning my credits? Peak clown-tier business move. I'm unsubscribing after this month; I'd rather pay a premium for something that actually works. 🤯 |
Beta Was this translation helpful? Give feedback.
-
|
Started working as of today, after a bit of usage, several including me got hit with the 20th 2AM / 08:00. Funny (as all got now the same) |
Beta Was this translation helpful? Give feedback.
-
|
same #192880 |
Beta Was this translation helpful? Give feedback.
-
|
You triggered GitHub's distillation/abuse detection, the extended cooldown (24 to 48 hours is the common window) is the enforcement action, not a normal rate limit. The combination that usually sets it off is the same account hitting Opus or another premium model from multiple concurrent sessions, especially when the traffic pattern includes a VPN or a datacenter-adjacent IP. The system can't tell you apart from someone farming credits to resell. A few things worth knowing:
For the support ticket, include the timestamps when you hit the limit, the tools/IDEs you're using Copilot from, and mention you were on a VPN for that quarter-hour window. That gives them enough context to look up your traffic and confirm it was a false positive. Refunds for paid Opus credits burned during the cooldown aren't automatic, ask for them explicitly. The messaging on GitHub's side really needs work though. Landing a "looks like scraping" dialog on a paying customer with no prior warning is bad product. |
Beta Was this translation helpful? Give feedback.
-
|
Sources? Sounds AI generated |
Beta Was this translation helpful? Give feedback.
-
|
To the GitHub Copilot Team, I am writing to express my strong dissatisfaction with your recent restrictions. Are you suggesting that a legitimate individual user running Copilot via remote control between remote and local environments is somehow "violating" your terms? This is an incredibly overbearing and unreasonable policy. As a paying subscriber, I expect the service to be available across my development environments, whether I am working locally or accessing my setup remotely. Restricting usage based on the method of access—especially when the intent is legitimate personal development—is a blatant disregard for user experience and a breach of the trust we place in a professional tool. Your current approach feels less like "managing service quality" and more like a forced restriction of a service I have already paid for. I demand a clear explanation for these "intelligence throttling" and access-limiting behaviors. |
Beta Was this translation helpful? Give feedback.
-
|
Aaaaand I'm rate limited again. Still no response to the support ticket that has been open 4 days. Perhaps it would be worth contacting a lawyer? Edit: Waited only 30 minutes, tried GPT 5.4 and it worked for a few minutes, then gave the 50 hour rate limit again. What is going on? |
Beta Was this translation helpful? Give feedback.
-
|
@Akash1134 Why hasn't GitHub put out a statement on this? Why are paying Pro+ users still getting these extreme rate limits? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, just reviewing code isn't even working anymore. Few iterations and limited. As of right now GHCP is useless for any more in-depth codebase analysis. |
Beta Was this translation helpful? Give feedback.
-
|
Ran into the same thing two days ago, hit a 38 hour cooldown on Opus 4.6 after maybe an hour of real work. Bit of what I've pieced together from going through it: The limit is per-account, not per-model. Switching from Opus to Sonnet while flagged doesn't do anything. Auto mode seems to bypass it but the output quality on longer agentic tasks drops off a cliff. Weirdest part for me was that the Copilot usage dashboard still showed me at around 20% of my monthly budget while I was hard blocked. Whatever signal is driving the cooldown isn't actually tied to the credit number the UI is showing you. For the support ticket, including exact timestamps and which IDE you were in helped me get an actual human response (took about 40 hours). Not a fix, but at least an acknowledgment. Really hope they add a visible counter for this, flying blind on when the block lifts is the worst part. |
Beta Was this translation helpful? Give feedback.
-
|
Copilot CLI ● Changelog for v1.0.32
Auto in Copilot CLI works under /model |
Beta Was this translation helpful? Give feedback.
-
|
The problem is that these "weekly usage limits" shouldn't exist in the first place, because what's the point of paying for a service and paying for premium credits if I'm not allowed to use them? |
Beta Was this translation helpful? Give feedback.
-
|
Same here. |
Beta Was this translation helpful? Give feedback.
-
|
GitHub Support replied, but the response was mostly a restatement of the docs. I understand that global rate limits exist and that premium models have capacity constraints. That part is clear. What is still not clear is:
That short retry timer is the most frustrating part, because in practice waiting does not reliably solve anything. If the real reset window is much longer, the UI should say so instead of showing a tiny retry countdown that often changes nothing. I also saw the problem not only in one huge session, but in newly created sessions too. So this does not look like a simple “your chat got too long” case. At this point the issue is not just the rate limit itself — it is the lack of a clear explanation of how it actually works. |
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.
-
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Copilot in GitHub
Body
When did these become a thing? I'm a Pro+ customer who consistently pays for hundreds worth of extra Claude Opus 4.6 credits per month. I might consider cancelling if this isn't a bug because I cannot afford to be hung out to dry for days at a time.
I tried switching to Opus 4.5, then Sonnet, but nothing budged.
After a while I attempted to start a chat using the web interface, only to be met with an suspicious half-accusation of scraping:
I've opened a support ticket but was wondering if anybody else has had similar issues? I frequently use Copilot in 1-3 windows simultaneously and used it under a VPN for a quarter of a hour or so earlier.
Beta Was this translation helpful? Give feedback.
All reactions