Copilot CLI 1.0.* consistently triggers rate-limit error after update

[gregvisma]

Hello,

Since updating to Copilot CLI 1.0.6, I have been consistently hitting the following rate-limit error:

✗ 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 1 minute. Please review our Terms of Service 
  (https://docs.github.com/site-policy/github-terms/github-terms-of-service). (Request ID: 6477:3ECE38:260F5B7:2AC9285:69B9352C)

This started occurring after the update, and I am now seeing it repeatedly.

Could you confirm whether:
• there was a change in rate-limiting behavior in version 1.0.6,
• this is a known issue,
• or whether additional configuration or usage limits now apply?

If helpful, I can also provide more context about my setup and usage pattern.

Thanks.

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

[davep]

For what it's worth, a couple of times this morning, via the web only, I've had similar, only I get told I need to wait <duration>.

I've barely done anything with Copilot this morning; nothing compared to some sessions over the past few days.

[OotTheMonk]

I'm also seeing this issue in the Visual Studio integration after updating:
Sorry, you have been rate-limited. Please wait a moment before trying again. [Learn More]

Server Error: Sorry, you've exceeded your rate limits. Please review our [Terms of Service]. Error Code: rate_limited

[nehSgnaiL]

same <duration> with no clue

[steven140811]

我在更新后 Visual Studio 集成中也遇到这个问题：抱歉，你被速率限制了。请稍等再试。[了解更多]

服务器错误：抱歉，您的速率已超出上限。请查看我们的[服务条款]。错误代码：rate_limited

same problem

[ahai6700]

I also get the same errors / rate limits. Now much more often than even 2 days ago or even weeks before:

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 . Please review our Terms of Service (https://docs.github.com/site-policy/github-terms/github-terms-of-service). If the problem persists, please contact GitHub Support, including the request ID xxxxx. To retry, leave a comment on this pull request asking Copilot to try again.

[SpaghettiMaster545]

I can also confirm having this issue, before I was also getting rate limits but this was very rare and the issue seemed to disappear fast. But now i get them after only a few prompts, was there some change ? (I'm on Copilot pro free trial subscription)

[userofit123]

I have been getting it all day, I have barely been able to even use Copilot today. Now, it does nothing, I get the "Sorry, you have been rate-limited." message right away when I send a message to chat in VSCode.

[bigbruno]

I use Visual Studio Code Insiders and in the last few days the rate limit problem started, but today it has become impossible to use Copilot, it's rate limited almost all the time.

[NengxingGUO]

I am using GitHub Copilot in VS Code, and I am frequently encountering the following error:

"Sorry, you've exceeded your rate limits. Please wait a moment and try again."
Error code: rate_limited

This issue occurs repeatedly during normal usage and severely disrupts my workflow. It is not an occasional error — it happens very frequently throughout the day.

[Br1an67]

+1 here. Using Copilot CLI 1.0.7 on macOS.

Same error

Didn't have this issue before the update. "Wait 2 hours" is pretty excessive for normal usage.

[roojay]

Service is basically unavailable.

[keshav-imsafe]

Even I'm experiencing the same issue

[Smartesider]

I keep getting:
Sorry, you have been rate-limited. Please wait a moment before trying again.

Server Error: Sorry, you've exceeded your rate limits. Please review our

No matter which model i use. CODEX works just fine with the openai addon, but not copilot with the same model (or any other), been like this for two hours now.

[Lok17]

same here

[Smartesider]

Nice to hear I'm not alone. Thank you :)

[yufei0421]

[xorets]

For a third day in the row that "rate limit" problem hits so bad, that Copilot is almost unusable. It is so unreliable, that I already think that we need to switch to Claude Code. I would appreciate an acknowledgement of the problem beyond standard "your call is very important to us".

[txgx-pge]

This has been the most fantastic tool I've ever used for coding. I've made years of progress in only months. But right now I can't work. I get two or three minutes and then rate-limit with at least 15-20 minutes before I can try again successfully. I've signed-out and back in, I've restarted VS Code multiple times, rebooted multiple time. Happens on my corporate client account, my company account, and my own personal account.

It's not cool to be in the middle of a long-running, delicate operation and have copilot halt everything mid-work and not let me continue until some seemingly arbitrary point in the unknown future. You should give us some kind of indicator when we're getting close to such limits. And 'Try Again' should never cost us credits - most of the time it's a problem on your end. And I consider this a problem on your end, since you can't/won't ever tell us how close we are to that limit.

[forX01]

Start getting the issue (with a GitHub Copilot Business subscription)
I use VS Code
I'm able to ask when I use the web interface (https://github.com/copilot)
I tried different pc with different internet ip adress.

[mfrank4101]

I’m using VS Copilot Pro (paid) and just started running into the same rate-limit error. I tried switching models—including Auto, which GitHub recommends when hitting rate limits—but that didn’t resolve it. What did work (at least for now) was signing out of GitHub in VS Code (including Copilot/Copilot Chat) and then signing back in.

[congzhang0]

Today is the fourth day I've been affected by rate-limit in VS Code.

[Smartesider]

Same here. I'm getting VERY fustrated. Can't do any real work. Because when it stops, it affects all models, not just one like before. Anyone heard anything?

[pglejzer]

I have the same problem...

[brichardson2x]

In this thread, a few others and recently in my support thread they trotted out a copy-paste excuse.

https://github.com/orgs/community/discussions/180092

But I'm pretty sure they just broke something in copilot because the limits affect everyone regardless of usage seemingly.

[wanzhao0]

This error appeared in less than 30 minutes.Therefore, what issue occurred on your servers?

[middeee]

I have also been seeing this lately. This is very frustrating, since other services don't cause rate limiting like this. (Claude, etc.)

[ahai6700]

it still hasnt been resolved....however I found this statement, if you guys are interested in it:

https://www.reddit.com/r/GithubCopilot/comments/1rygfjb/copilot_update_rate_limits_fixes/

[niostack]

I'm also experiencing this issue. My very first request after waking up today triggered this rate limit, even though I hadn't made any requests in the previous 12 hours.
`✗ 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 4 hours. Please review our Terms of Service
(https://docs.github.com/site-policy/github-terms/github-terms-of-service). (Request ID:
DA31:20ED04:2FCE24:38395A:69C5F045)`

[niostack]

I was able to start working again after waiting for four hours.

[vn-vna]

I have updated to the latest version 1.0.12 for 30 minutes and instantly got rate-limit hit.

[RADLEWIS]

I meet it too, but I only send 2-3 requests to copilot before meeting this problem:(

[Moliboy5000]

Experiencing the same too after 2-3 prompts. Never happened before.

[AbhishekGhoshdev]

Issue Description

When it occurs: Only in multi-CLI mode when /tasks or agents running in parallel hit rate limiting.

How to identify it: The CLI can report when rate limiting is active, but only in multi-CLI mode with parallel agent execution.
Root Cause

The system lacks a controllable harness to manage rate limiting. The architecture doesn't allow models to run in parallel while implementing intelligent rate-limiting strategies.
Problem

Parallel execution without load-aware rate limiting — agents get rate limited even after payment, which creates a poor user experience.
Recommendation

The architecture should:

Allow models to run in parallel
Implement rate limiting only during high-load periods
Avoid rate limiting paid users under normal load conditions

[Bhavesh1116]

Perfect, ab solid answer de sakta hoon. Ye post kar:

Hey! This isn't specific to CLI 1.0.6 — it's a broader GitHub-side issue that's been affecting many users.
What actually happened: On March 16, GitHub discovered a bug in their rate-limiting system that had been undercounting tokens from newer models like Opus 4.6 and GPT-5.4. When they fixed the bug, it restored limits to previously configured values — but since these newer models are much more token-intensive, the fix ended up impacting users with completely normal usage patterns. GitHub
So it wasn't a CLI version change causing this — it was a backend rate-limit recalibration that hit everyone using premium models hard.
What GitHub is doing about it: They're rolling out per-model limits (with higher-tier plans getting higher limits), investing in UI improvements to show usage before you hit the wall, and working to ensure rate limits rarely impact normal users going forward. GitHub
Workarounds for now:

Switch to Auto model (not subject to model-specific limits)
Use GPT-4.1 or GPT-4o for lighter tasks (included models, no premium request cost)
Update to CLI 1.0.15 (latest stable) — fixes several unrelated stability issues

For compensation, contact GitHub Support with your affected session dates.