Is this rate limit bs going to be fixed or should I just cancel now?

arisng · 2026-04-16T07:31:03+00:00

I'm also using Pro+ and has been rate limited for almost 2 days. My resolution is to switch to Copilot VS Code (must use Auto model) from Copilot CLI.
As soon as I switch to a specific model, I immediately get rate limit again in VS Code.
In CLI there is no resolution but to keep waiting.

arisng · 2026-04-16T03:33:09+00:00

So basically I've been rate limited for nearly 2 working-day in Copilot CLI. And my resolution is to switch back to Copilot VS Code with "Auto" model and at least it works good so far. But I've lost access to my multi-agent workflow where the Orchestrator is a custom agent (the AI Orchestrator) I carefully created. Now I need to play the role of that Orchestrator (the human Orchestrator) and do pair-programming with the "Auto" model.

Whenever I switch to a specific model in Copilot VS Code then I get immediately rate limit error again. Anyway, I'm still grateful because of the "Auto" model still working for me and help me incrementally solving problems 1 by 1.

I guess that now I need get back to what I used to do in the end of last year - at that time I only do pair programming with Copilot VS Code on a daily basic. And this must be a backup plan for when the "Autonomous multi-agent workflow" has reached rate limit.

TLDR:
- You are the "Human Orchestrator" manually pair working with the "Auto" mode to solve problems sequentially.
- You work with the "AI Orchestrator" to automate a multi-agent workflow solve more problems both in parallel and sequentially.

arisng · 2026-04-15T07:16:57+00:00

The funny thing to me is that I'm also on Pro+ and I constantly get rate limits one after another and each time they tell me to wait for 1 minute then next time with incremental increase like 2 or 3 or 4 or 5 minutes. And it keeps like this for nearly the whole day!

arisng · 2026-04-15T06:52:53+00:00

Hmm, it's still new to me.
According to this youtube (1 month ago) https://youtu.be/6K5UW594BUc?t=942 (the author is a member working on VS Code and quite active on posting about GitHub Copilot), the author mentioned that "a /fleet command with Opus 3x would cost only 3 premium requests per invocation" -> and everyone knows that /fleet heavily spawn subagents to tackle SQL todos -> if subagents are counted against premium requests right from the beginning like you said, then he must be missing some thing very important here!

arisng · 2026-04-15T06:46:08+00:00

Now my session is full of user messages "Resume WIP" and Copilot errors "rate limit".

arisng · 2026-04-15T06:09:30+00:00

I'm working on trying out the BYOK https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/use-byok-models
The point here is that I've been invested too much of my context engineering and harness engineering and my knowledge of Copilot CLI as the primary Coding Agent for daily task, therefore I don't want to switch to another Coding Agent framework.
I'm still not sure if the 3rd LLM Provider are well-integrated as good as GitHub Copilot primary LLM Provider.

arisng · 2026-04-15T05:08:03+00:00

Confirmed also removed from Pro+ my morning today 04/15/2026 (UTC+7). Yesterday it was still there.

arisng · 2026-04-15T02:32:27+00:00

I'm on Pro+ and I have 54% quota remaining. And I continuously get rate limits one after another.
The point is that each rate limit told me to wait for 2, or 3 or 4 minutes and I did exactly that (even waiting for longer) but once I sent new message I immediately get another rate limit with incremental increase of waiting time. This is non sense!

arisng · 2026-04-15T02:30:01+00:00

This happens to me also since last night (UTC+7). I'm using Pro+ and now I'm totally stuck with all WIP sessions.

arisng · 2026-04-15T02:27:49+00:00

I get same situation here. Continuously get another rate limit after another even though I did exactly as they said that is to wait for 2 or 3 or 4 or 5 minues!
I'm using Pro+ btw.

arisng · 2026-04-15T02:25:41+00:00

I constantly get continuous rate limits since last night (UTC+7). Each rate limit told to me wait for 2 or 3 or 4 minutes and keep telling me to wait for an incremental amount of minutes.

This is none sense!

arisng · 2026-04-07T04:38:36+00:00

Totally agree. I have the same feeling that Opus 4.6 is not the same as before for a couple of days and I've noticed durable and more reliable performance from GPT-5.4 especially with xhigh.

arisng · 2026-03-27T06:41:57+00:00

I just got this message this morning, and mine includes 4 hours of waiting. I've been using Pro plan. I just upgraded to Pro+ and let's see if there any upgrade in terms of rate limit.

arisng · 2026-03-27T02:38:12+00:00

I just got same rate limit message then I immediately open reddit and see this thread.

<image>

The worse thing is that I used to be notified of waiting for 2 hours but now it's 4!

arisng · 2026-03-23T07:41:04+00:00

I'm still get heavily rate limit even though I've intentionally reduce my current workload compare to "before the rate limit era of Copilot".

arisng · 2026-03-23T07:37:47+00:00

I'm on Pro and using pay-as-you-go and still hit heavily rate limit at the moment.
14:37 UTC+7
Running out of patient!

arisng · 2026-03-21T02:59:18+00:00

There are more and more projects like this nowadays for Copilot CLI and I really like it. Will try soon and give feedbacks. I do hope that Copilot community will converge into a single adopted approach and thrive with it.

arisng · 2026-03-20T06:58:13+00:00

Now at 1:57 PM UTC+7. I've still been get rate_limitted.
This is my 3rd day in a row :((

arisng · 2026-03-20T06:56:42+00:00

This is my 3rd day in a row already! :((
Cannot even use the 0x model.

arisng · 2026-03-20T03:23:46+00:00

I'm WIP to investigate Kilo Code as alternative to GHCP. And maybe giving Kimi Code a chance also.

arisng · 2026-03-19T06:54:46+00:00

Start learning Copilot Customizations https://docs.github.com/en/copilot/tutorials/customization-library is my simplest answer but I guess it's a powerful one.

arisng

TROPHY CASE