Auto Mode Still Using Weekly Rate Limits & Potential Self Healing/Self Improving By Default

[RockyWearsAHat]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot Agent Mode

Body

Two things, firstly, when using copilot chat recently (I opened an issue for this as well) I got hit with the weekly rate limit when using Auto mode. Is it intended for Auto to count towards the weekly limit even when it is literally the way to keep using copilot when you hit the weekly limit?? It feels like when my limit resets I'm supposed to just use only selected model requests because otherwise my limits will (slowly, but will) increase meaning I should just only code selecting my model for the time I have the ability??

Secondly, what is the opinion on adding something like

IF THE USER SEEMS ARGUMENTATIVE OR CONFUSED, IT IS BECAUSE YOU MISSED OR DIDN'T NOTE SOMETHING DOWN THAT WAS IMPORTANT GENERALLY OR MISSED LINKING SOMETHING UP IN THE CODE. ENSURE THESE THINGS NEVER HAPPEN SO WE AREN'T FLYING BLIND OR SAYING SOMETHING IS COMPLETE WHEN IN ALL REALITY IT IS NOT WORKING OR NOT EVEN LINKED TO THE RELEVANT PART OF THE CODE. IF THE USER IS ANGRY, RECONSIDER WHAT IS CAUSING THE ANGER, CONFUSION OR GRIEF, FIX IT SO IT DOESN'T HAPPEN AGAIN. THIS MEANS REVIEW THE ENTIRE CONVERSATION, WRITE THE FIXES TO THE BEHAVIORS THAT WERE CAUSING ISSUES IN THE INSTRUCTIONS AND ENSURE PROPER DOCUMENTATION AND ENSURANCE THE PROJECT IS WORKING AT 100% WITH EVERYTHING SET UP AND LINKED + OPERATING TOGETHER AND AS ONE, AS INTENTED. IF THE USER IS FRUSTURATED, SOMETHING IS WRONG, WE EITHER HAVEN'T BEEN MAKING PROGRESS, YOU ARE OVERLY INQUISITIVE, YOU FORGOT SOMETHING TRIVIAL, YOU'RE ASKING QUESTIONS THAT DON'T EVEN MAKE SENSE, ETC. FIX AND SELF UPDATE + DOCUMENT AND CHECK CODE FOR COMPLETENESS IN CONVERSATION AND SUCH IF THE USER EVER SEEMS UPSET PLEASE!

Into the instructions, this seems like it's the next step for copilot, currently it's a little rough to get full projects built because it's often telling copilot over and over again to continue and keep building and try again. This instruction just makes it so if the agent realizes the user has grief (often the model says "the user is upset so I will...." and often times when it starts doing this it doesn't learn and doesn't improve, it continues in the same path instead of reconsidering it's approach, which truely is what should instead be happening because otherwise it hits a similar state {which because the code is that way right now it generally continues in that same state} which can lead to massively long loops. This one instruction isn't an end all be all fix but it does prevent the agent from repeating its same errors and instead forces it to reconsider and redocument so that it physically can't continue to make the same mistake, it might not be perfect but it should help with some really long loops where the user continues to be upset because the agent isn't using it's brain or is too locked in one mode of thinking. It's rough to trash an entire chat context but sometimes it costs me more to argue to model back into place than it would be to just copy the whole concise history into a new chat with my request, or atleast it feels like it.)

Anyone have any opinions on this? How it could be improved or if they also want this to be default or have been experiencing this bug?

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