Ascii freindly output should be default

[duane5000]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

The core ask is straightforward: when the output target is a shell script, constrain character output to printable ASCII (0x20-0x7E). No em-dashes, no box-drawing, no smart quotes, no ampersands in string literals for PowerShell.

I've saved the rule in my persistent memory so it applies to all future sessions with you, but that's a per-user band-aid - not a platform fix.

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

[duane5000]

These LLM are expected to be learning from these experiences, but there there are things like this that repeat so often, it appears to need to be told explicitly what not to do. I can't count how many prompts I've repeated just to fix something that the session has seen broken and should have been obvious not to repeat. My usage tokens get eaten up quickly by this sort of buggy behavior and should be something that is monitored and adjusted programmatically. If a type of error occurs repeatedly, it should be discounted on a per-account basis