Copilot rate limit but i have PRO licence !!!

[JulieRaymond]

Select Topic Area

Bug

Copilot Feature Area

Copilot in GitHub

Body

I am the pro version, and i have this message :
"
Sorry, you have been rate-limited. Please wait a moment before trying again. Learn More

Server Error: Sorry, you have exceeded your Copilot token usage. Please review our Terms of Service. Error Code: rate_limited
"

Please resolve it.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[AlexPrincipal]

Was it a worldwide outage?

[AlexPrincipal]

yep, it’s back here too

[dkwkzz5252-cyber]

저도 동일한 문제가 있어여 ㅜㅜ

[bogdan-coman-uv]

Same issue, regardless of the model: You've hit your global rate limit. Please upgrade your plan or wait for your limit to reset.
Do we need $200 USD / month subscriptions now to actually do work with copilot?

[jtanghkpu]

I have the same issue! =(
Please fix the bug!

[JulieRaymond]

And my profile indicates only :

[toinemini]

+1. I am even on Pro+. I am also rate limited for 3 days :D

FYI, I am on Pro+ and have only hit 14.0% usage FOR THE MONTH so far. Completely unbelieveable! I am not a heavy user at all.

[novello-dev]

this message usually means you hit a short-term rate limit, not your monthly quota. the usage bar on your profile updates with some delay, so it can easily show something like 10–15% while the backend has already throttled you for a burst of requests.

copilot has two separate limits:

the monthly premium allowance (the bar you’re seeing)
and a per-minute / per-hour rate limit to prevent too many requests at once

the error you posted matches the second one. it usually clears on its own after a short cooldown. if it keeps happening even with light usage, it might be the extension sending a lot of background requests without you noticing.

give it a bit of time and it should work again. if it doesn’t, try restarting the editor or checking if any plugin is spamming copilot in the background.

hope this helps! and if it solves it, feel free to mark the thread as answered so others can find it later.

[abhisheksiddhu]

I am also getting it very frequently when assigning multiple issues to coding agent, only coding agent is using the requests. any way to increase the limits like a higher plan. it's really frustrating and negates the purpose of an autonomous agent if i have to come online after every 2 hours and restart the agent. i understand rate-limits are necessary but then at least have a way to schedule auto-retry for coding agents if rate-limited after the cooling period.

[a-man-called-q]

I am also getting it very frequently when assigning multiple issues to coding agent, only coding agent is using the requests. any way to increase the limits like a higher plan. it's really frustrating and negates the purpose of an autonomous agent if i have to come online after every 2 hours and restart the agent. i understand rate-limits are necessary but then at least have a way to schedule auto-retry for coding agents if rate-limited after the cooling period.

IMO, rate limiting is to prevent DOS attack I think. I also hit rate limits sometimes. from your words assigning multiple issues to coding agent it seems like the work around is to separate those to multiple agents ? I did that sometimes

[abhisheksiddhu]

In the hosted agent, we just assign issues in Github to copilot and it'll start an agent automatically hosted on Github actions. I face the rate limit less frequently if I only assign one issue at a time, but then I have to come online every few hours and assign the next task.

I know that rate limits are needed, that's why I am suggesting to have a feature to queue tasks automatically.

What I want is that I plan an epic with multiple sub-issues with details laid out, assign them all to copilot, come online after a few hours or next day depending on the amount of work, review the generated code and move on. Github should do the queuing starting stopping of agents without my manual intervention.

[nathanielx044-gif]

I’m running into the same problem as well. When multiple tasks are assigned to a coding agent, rate limits tend to interrupt the workflow and reduce the overall usefulness of automation.

I do understand why limits exist, but it would really help if there were either higher thresholds on paid tiers or some kind of automatic retry after the cooldown period. Having to manually restart the agent each time kind of breaks the idea of an “autonomous” system.

I’ve also been exploring workflow automation approaches for handling such limitations more smoothly.

[caudurodev]

Can more transparency be added so we can keep using your api instead of having to look elsewhere? If you added - you need to stay under x requests per minute or wait 10min/1h etc to continue it would be a much better devx

[novello-dev]

+1 for this...

[Obazzi]

Can we estimate how many per hours we can do before we hit the ratelimit? Would be useful for my Ralph script to put the right amount of sleep between the runs. Actually, could make a ralph script that detects the ratelimits and log them and also progressively make less requests per hour until it doesn't get rate limited anymore....

[advicee12]

Do github respond xDD like i bought pro yestoday and after 1 hour and 2-3% requests got rate limited until today xDDDD like today i work for 1 hour and rate limit again xD whats the point to work if you can't work longer than one hour, then you have to wait another 2-5 hours ....

[Florin7222]

make less requests per h

Did you do that? would need some help on that cause i am on the 40 dollars plan and funny enough i hit every rate limit, the temp ones, the monthly and recently, the weekly one.. like what.. to use my 1500 requests i need to spend alot of hours on my computer and if i do, i get rate limit daily and weekly. my point being, they make it hard for me to reach my full credit/request with all those limits

[Echostorm44]

I am getting this too and it seems like a you problem. I have 1 instance of Copilot CLI running and doing 1 thing yet I bump into this maybe once or twice a day. It leaves me mid job so I have to dig around and figure out what is now half done or broken and I suspect it is eating a premium request. I don't have any control over how much the AI makes calls but you guys do. You could at least handle this gracefully instead of crashing out mid request. Paying Pro+. I glance over and I see a page of these.

` ✓ Edit ThreeStageFFTConfig.cs

✓ Edit DebugCarryFusedIsolated.cs

✗ Model call failed: {"message":"Sorry, you have exceeded your Copilot token usage. Please review our Terms of
Service.","code":"rate_limited"}
(Request ID: F3E8:12948C:2968905:2FAE35B:694165D9)

✗ Model call failed: {"message":"Sorry, you have exceeded your Copilot token usage. Please review our Terms of
Service.","code":"rate_limited"}
(Request ID: F3E8:12948C:2974A43:2FBB911:69416605)

✗ Model call failed: {"message":"Sorry, you have exceeded your Copilot token usage. Please review our Terms of
Service.","code":"rate_limited"}
(Request ID: F3E8:12948C:297CDED:2FC4B02:69416624)`

[Mikk2580]

Same problem here. I get a lot of rate-limited with ONLY ONE AI working on the project.
i really want to support GitHub/copilot, really...... but the UX is not great, no indication what is going on with AI, usage monitoring and no way to fine-tune your AI usage settings. The throttle before the rate limit would be much better solution but right now it just stops.
This is not great experience and feels a broken system. With this it give a reason to search better options with competitors.
Dont be NOKIA ("We didn't do anything wrong, but somehow, we lost").... fix it before it is too late.

[dbeattie71]

I've run into this and have yet to find the setting that lets me pay for more. Please take my org's $$ and let me continue. I instead end up stalled halfway through the plan. Has anyone tried BYO model to get around this?

[kszpirak]

Just run into this exact same wall. Sorry, you have been rate-limited. Please wait a moment before trying again. Learn More

terrible. I can't work like this; same idea; let me pay for more request and freaking take my money let me continue the work.

[SarahRoseLives]

✗ Model call failed: Sorry, you have exceeded your Copilot token usage. Please review our Terms of
Service. (Request ID:
A572:333BC0:50252FC:68A5913:69560085)

✗ Execution failed: 429 Sorry, you have exceeded your Copilot token usage. Please review our Terms of
Service.

Such a helpful error -_-
I feel like switching to another AI because idk what it's even down for... is this rate limiting or something else?

[yassineMouttalib]

{ message:
'Sorry, you have exceeded your Copilot token usage. Please review our Terms of Service.',
code: 'rate_limited' } }
deosnt specify how much time should wait, just normal usage no concurrency and i get this error its not normal.

[Rockhelljumper]

I'm running into this too, and even waiting several minutes, I still get the same rate limiting error with a copilot enterprise account. Your terms of service do not show any rate limit values, just that you will be rate limited if you violate TOS.

[IAMprodigi]

They are apparently throttling Pro accounts, making the chat completely unusable. Terrible management and product experience.

[Wulfic]

yeah and it eats up your overall usage, so you can get halfway through a chat session and it just stop midwway withh your code butchered and then they count it against you anyway. im getting ready to switch directly to anthropic or something. its a total waste of time and energy with the new changes they made recently

[umezakip]

Just another reason for me to cancel my subscription. Theyre getting to greedy.

[reapercanuk39]

Model call failed: Sorry, you have exceeded your Copilot token
usage. Please review our [Terms of Service](https://docs.github.co
m/en/site-policy/github-terms/github-terms-of-service). (Request
ID: 90E2:1C68C2:F8DEB:119647:69667B7C)

Meanwhile I've got pro, and added 500$ budget with my creditcard because I use this a lot
But yet I'm no where near my budget and still getting this message

[KlomDark]

Yeah, this is nonsense. I'm here cause I'm currently wasting time waiting for the throttling to reset. I gave it one task: to refactor a class that had grown into a god class. I've hit the rate limit twice on the same task now. Maybe it should look at the request scope and at least say "Sorry Dave, I can't do that" rather than the unfriendly/useless way it's handling this issue. I've got a pro plan and there's a lot of credit left on it, so this is unacceptable. Do better.

[alexmatjuhin]

I'm here because of the opposit problem: around 400 Queries and Commands with duplicated logic which I moved into the middleware in my pipeline so the only thing I've asked is to remove those duplicates and refactor the rest a bit to follow common principles and the latest C# syntax sugar. And boom! The chat hangs with 429 error In the middle of refactoring pack of next 10 files. Monthy usage is 47%. Every metric here is in "included" zone. Those hourly and daily limits should be more clear!

[AdvayRChandra]

I have also run into this issue multiple times before. Usually, this happens after excessive usage of one of the more premium models. A good way to tell this is to look at the right-hand side of the model selection UI:

The number that you see on the right indicates the current amount of rate usage a model consumes, and a more premium model (ex. the Claude 4.5 Opus I am using) will have a higher number, and thus hit the rate limit faster. Do not worry, because they usually reset within 24 hours, so you should gain access soon.

[KlomDark]

If I was driving my car on the interstate and it randomly, with no warning, just pulled to the side of the road and made me wait 24 hours to drive again, I would certainly not find that acceptable. Luckily it seems the reset is usually at the top of each hour rather than 24 hours. But this is still unacceptable for a paid plan. If it was free I'd understand, but it's not free.

[elihuvillaraus]

Can not agree more! Those who say "Just wait" do not understand that this is work, money, pro stuff, not hobby nor games.

[ehendrix23]

I don 't think it is ever going to be removed. I was supposed to be not rate limited anymore 17 hours yet I am still rate limited.

I had received a rate limit of 51 hours:

{"errorType":"rate_limit","message":"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 in 51 hours. Please review our Terms of Service (https://docs.github.com/site-policy/github-terms/github-terms-of-service). ","statusCode":429,"timestamp":"2026-04-14T01:56:31.150Z"}

which means wait until 2026-04-16T05:10:41.482Z

It is now 2026-04-16T22:15:00Z (16:15PM local time) and I'm still rate limited.
When I had tried it gave me:

You've reached your weekly rate limit. Please upgrade your plan or wait for your limit to reset on April 16, 2026 at 2:00 PM

When I try later again I get:

You've reached your weekly rate limit. Please upgrade your plan or wait for your limit to reset on April 16, 2026 at 2:15 PM

So I wait few hours and then have it try again. Now it says:

You've reached your weekly rate limit. Please upgrade your plan or wait for your limit to reset on April 16, 2026 at 4:22 PM

And no, I haven't done anything with it in the mean time. Just been waiting.

[davidbrend]

UPDATE: It looks like it's starting to work!

2 requests and it didn't hit the rate-limit on the Pro+ subscription!

Don't shout it out and hope for proper functionality!

[davidbrend]

@cyrus1010d-max Pro+
But! big but. After a full day of use (not small requests) I got another block: “Service is currently limited. Please wait a moment and try again in 175781 seconds. Request ID: d22ee4a2-7654-4e3f-bfc0-9bc0f42ca564”
Something around $13 (180 requests with their pricing) for all premium requests and they blocked me again.

Interesting, the ones you ran, they worked fully, or no? Last month before I cancelled, it would constantly stop with rate limits of 15ish seconds, or stop without explanation, making it burn 3-20x the requests.

It worked perfectly, in the one whole day that I did some work, I didn't see any sign of slowdowns, limits, or anything. Only now, after about 180 requests according to their report, I got a limit.

It seems to me as if they added a rate-limit function without warning like Claude and others have.

[pepperymilkcap]

Ditto for me also. Hit with a 44 hour rate limit a few days ago, now another 50 hour one when I start trying to do work.

[Santiagorich]

@davidbrend On my end I can only use auto, even thinking about selecting a model will get me rate limited, I can't get a single request through even on new chats, fully unusable, and it has been like this for days, the model "auto" is using is really bad, a bunch of bad practices, bad design, etc, etc

The entire thing is unusable, i'm just copypasting into gemini and other tools atp, i'm giving this 1 more day or i'm cancelling my annual subscription and requesting a refund

[cloudify]

@davidbrend On my end I can only use auto, even thinking about selecting a model will get me rate limited, I can't get a single request through even on new chats, fully unusable, and it has been like this for days, the model "auto" is using is really bad, a bunch of bad practices, bad design, etc, etc

I'm exactly on your same situation, have not being able to use copilot with any model at all last week, no one single request worked, all rate limited, even copilot review gets rate limited.

[davidbrend]

@Santiagorich I honestly don't give it even one day. I'm slowly but surely moving to Claude Code for the advanced work + Windsurf chat, where free models like SWE-1.6 or Kimi K2.5 (for basic work) run (even Windsurf "auto" mode is better then this).

In my calculations, it looks like Max 5x with the right settings (even a 20x Claude Max subscription) will be much more efficient and better than Copilot with these restrictions.

It's clear that until Copilot makes an effective and clear structure for limitations (= best to completely remove it), I won't go back.

And I believe that the vast majority will leave like this too - in similiar way.

[Silicom-11]

que es esto???

[Download]

it seems like a you problem

Yeah, the many reactions here sure suggest user error...
He must be the only one experiencing it...

What nonsense 👎

[toinemini]

I am also rate limited for 3 days :D

FYI, I am on Pro+ and have only hit 14.0% usage FOR THE MONTH so far. Completely unbelieveable! I am not a heavy user at all.

[ehendrix23]

Was going for a little bit, and now rate limited again for 1 hour and 2 minutes. Only thing really I've been having it do is review code. That's it. Once reviewed I went to Codex to resolve issues, and once Codex resolved went back to CoPilot to do new review.
Had 2 of these kinds of sessions going but obviously with times in between due to then going back to Codex to resolve.

I do not see how with these rate limits anyone can even get close to 1500 premium requests unless your prompts are like: "Analyze the code in function x between lines z and y). Or "Change this variable on this line to this" so that each prompts ends up a very simple request instead of the push to have AI accomplish a complete task.

[RayFungHK]

switch to Opus 4.7, 90 request, rate limit 88minutes
Github you are genius, only takes few months to kill your products.

[JulieSapir]

Yet another limit on another account.
Waiting for hours or it will be weekly limit :(

[mourad1081]

Up Urgent, same issue here

[hrkisk]

Literally just 18 requests to GPT-5.4 in a span of 8 hours and yet stupid ratelimit for 50hours!!! WTF?

[willresen]

Copilot Pro+ here. $40/month for weekly limits?

[Coekjan]

copilot pro+ here, my usage is very stable and reached 50% at Apr 15. But at Apr 16, I received rate limit and had to wait 3 days for continuation. Insane...

[KlotzJesse]

Copilot CLI

● Changelog for v1.0.32

• Select auto as your model to let Copilot automatically pick the best available model for each session
• Add --print-debug-info flag to display version, terminal capabilities, and environment variables
• Show warnings when approaching 75% and 90% of your weekly usage limit
• Attach supported document files to prompts for the agent to read and reason about
• Add --connect flag to directly connect to a remote session by ID
• /feedback saves the bundle to TEMP when the working directory is not writable
• copilot login --host now correctly authenticates with GitHub Enterprise Cloud (GHE) instances
• Current date and time in agent context now includes local timezone offset
• Terminal progress indicator stays visible while the agent is thinking
• Status line no longer shows stray Unicode glyphs in terminals like Neovim after /clear
• Rewind works correctly after using /cd to change directories
• Multiline input is preserved when using /plan and plan mode
• Backspace correctly exits shell mode only when the input is empty
• Mouse wheel scrolling works correctly in the /ask dialog
• Allow short session ID prefixes (7+ hex chars) with --resume and /resume instead of the full ID
• Rate-limited sessions now pause queued messages and automatically retry instead of dropping them
• Tables render with correct column widths, emoji support, and stable borders during terminal resize
• Rate limit error messages now show specific context based on the type of limit reached
• Session idle timeout is now configurable via --session-idle-timeout; disabled by default
• Skills that exceed the token limit are still discoverable and invocable by name

  Error:
  You've reached your weekly rate limit. Please wait for your limit to reset on April 20, 2026 at 2:00 AM or switch to auto mod
 to continue. Learn More (https://docs.github.com/en/copilot/concepts/rate-limits). (Request ID: 
F24F:35D86:1386FD8:181ED23:69E31DCE) 

Auto in Copilot CLI works under /model

[jonathanGGa]

For me nothing is gonna change. I think there isn't any issue (for them), they're strictly applying their rules (https://docs.github.com/en/github-models/use-github-models/prototyping-with-ai-models#rate-limits (Pro+ could corresponds to Copilot Enterprise in the table)), so i downgraded from Pro+ to Pro (There is no reason to pay four times more if I cannot use the product four times as much). We've been talking about this for 4 or 5 days now, don't you think we would have already received help from Microsoft if it were a problem?

[themaoci]

those rate limits are straight up outraigious. i didnt paid for pro+ to be rate limited that hard even on free models... YES THAT COUNTS TO FREE MODELS AS WELL ITS GLOBAL THING. and on top of daily limits there is weekly limits that are not covered anywhere. additionally there is also another type of rate limits that is kinda hard to git but its also not covered in their terms of service which is violation of the license. which i will be charging back if they dont respond to my support ticket witheen a week. (i paid for a year 2 months ago)

[rodrigoslayertech]

The same here. I think this is global in the Github Copilot.

It's likely that AI providers for GitHub Copilot have cut off general access, and many users are hitting the limit even without using the available premium requests.

I'm already using the additional ones, but I'd never seen this rate limit before.

[mfakhoury]

AI providers have nothing to do with GitHub. The issue comes from Microsoft/GitHub, they are the ones who introduced these restrictions.