Is this a joke?: You've hit your session rate limit. Please upgrade your plan or wait a moment for your limit to reset

[litaniecontrelapeur]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Copilot Agent Mode

Body

[asaddevx]

Hi @litaniecontrelapeur , this is frustrating, but you're not alone. This is happening to thousands of users right now.

In Short : GitHub introduced new "session rate limits" on April 20 that are completely separate from your monthly request allowance. Your screenshot shows you have 97% of your monthly requests left, but you hit the session burst limit because you sent requests too quickly.

How to fix it:

1. Wait 1-5 hours — session limits reset automatically
2. Slow down — pause 30-60 seconds between prompts
3. Check GitHub Status — there's an active disruption making limits stricter

The hard truth: You did nothing wrong. GitHub changed the rules to manage server strain. This is the new normal until June 1 when usage-based billing starts.

Just wait a few hours and try again. It will reset.

[Bharani6]

It looks like you've hit the 'Agent Mode' burst limit. Even if you have 97% of your monthly quota left, GitHub limits how many sequential turns the AI agent can take in a single hour to prevent server overload.

Here is how to get back to work immediately:

Switch Models: If you are using 'Agent' mode, try switching back to the standard 'Chat' mode (GPT-4o or Claude 3.5 Sonnet). Standard chat often has higher individual burst limits than the Agent.

Context Cleanup: Clear your current chat session and start a new one. Sometimes the session limit is tied to the amount of 'tokens' being held in the current active window context.

Manual Mode: Instead of letting the Agent run everything, try asking it to 'Generate the code only' and you apply it manually. This reduces the number of background requests the Agent makes.

Hope this helps! If it works, please consider marking this as the answer so others facing this today can find the fix.