Edit/Agent Modes Lack Robust Error Recovery #159419
Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Copilot Feature Area
Copilot Agent Mode
Body
Edit or Agent mode lacks error recovery when the API is overloaded, context becomes too long or there are network i/o issues. This is often leading to cut-off prematurely aborted sessions with half-complete edits. I would like to see more robust ways of dealing with API errors.
Request
When backend errors occur, the problem is explained more clearly to the user rather than just a generic error message (context too long, network error, API throttling etc etc). Edits are either retried better or completely rolled back.
Beta Was this translation helpful? Give feedback.
All reactions