-
|
Hello, firstly thank you for the amazing tool. It's been a great help as my project grows and the code becomes more complex and chews up context super quickly. I'm not sure if this is merely by coincidence, so I'd like to know if anyone else is observing this error since adding the context-mode prompt to the copilot-instructions.
This is being done through Github's web agent session. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi @sthi-1005, thanks for reporting this! This is not caused by context-mode — it's GitHub Copilot's own rate limiting mechanism. Why it happensGitHub Copilot rate limits are request-count-based, not token-based (docs). Adding context-mode instructions to What you can do
This is an expected trade-off: context-mode helps you use your context window more efficiently, but that efficiency comes from more granular tool calls, which count against Copilot's request quota. Hope that helps! |
Beta Was this translation helpful? Give feedback.
Hi @sthi-1005, thanks for reporting this!
This is not caused by context-mode — it's GitHub Copilot's own rate limiting mechanism.
Why it happens
GitHub Copilot rate limits are request-count-based, not token-based (docs). Adding context-mode instructions to
copilot-instructions.mddoesn't directly trigger rate limits. However, context-mode's MCP tools may lead to more tool calls per session (batch executions, searches, indexing), which naturally consumes more premium requests — reaching the limit faster.What you can do