Copilot CLI - Request failed due to a transient API error - rate limit

[galluccipablo]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot Agent Mode

Body

It's my second day using GitHub Copilot Pro, and from my second request since I started using it, through Copilot CLI, I am constantly getting the error message Request failed due to a transient API error. Retrying....

In my last session, in addition to to the error message above, I got this one:

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: 9666:1776BE:2067F6:2C5E97:69C85B2B)

Only once this message about the rate limit has surfaced to the UI, but checking the logs in ~/.copilot/logs I can see many error messages with status 429, code user_model_rate_limited with the message Sorry, you've exhausted this model's rate limit. Please try a different model. Please review our [Terms of Service](https://docs.github.com/en/site-policy/github-terms/github-terms-of-service)., one entry for each time it showed the message Request failed due to a transient API error in the UI.

I'm seeing other users saying they are having a similar problem, although not with the same error message.

I'm using only 1 window/session, a very light use compared to what I have experimented with Claude or Codex. I really hope this is a bug and that it will be fixed soon enough, otherwise agentic coding with Copilot is unusable. I'm currently evaluating it as a replacement for my other coding plan subscriptions from other providers.

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