Describe the feature or problem you'd like to solve
When "Rate Limit" triggers, the current (potentially unattended) workflow aborts.
Proposed solution
Possible Solution/Workaround
Instead of rate-limiting, apply a reate-throttling, so the workflow does not abort.
E.g.: at 50% rate, throttle all further requests a bit, thus throughput goes down.
Note the fleet, subagents, unattended => all this is advertised copilot cli functionality.
So, if a user is n % too fast, throttle n % so usage goes down.
Please Realize
Copilot Cli is not usable currently, at least not for complex workflows, nightly research loops etc.
Todays update equals with "leave copilot cli behind, you can't produce with it"
Example prompts or workflows
No response
Additional context
User Struggles
check more user reports
https://github.com/search?q=repo%3Agithub%2Fcopilot-cli+rate+limit&type=issues
Describe the feature or problem you'd like to solve
When "Rate Limit" triggers, the current (potentially unattended) workflow aborts.
Proposed solution
Possible Solution/Workaround
Instead of rate-limiting, apply a reate-throttling, so the workflow does not abort.
E.g.: at 50% rate, throttle all further requests a bit, thus throughput goes down.
Note the
fleet,subagents,unattended=> all this is advertisedcopilot clifunctionality.So, if a user is n % too fast, throttle n % so usage goes down.
Please Realize
Copilot Cli is not usable currently, at least not for complex workflows, nightly research loops etc.
Todays update equals with "leave copilot cli behind, you can't produce with it"
Example prompts or workflows
No response
Additional context
User Struggles
check more user reports
https://github.com/search?q=repo%3Agithub%2Fcopilot-cli+rate+limit&type=issues