Feedback: github.copilot.chat.preferLongContext.enabled being enabled by default introduces cost, opacity, and performance concern #206292
Unanswered
Yamahari
asked this question in
Copilot Conversations
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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
VS Code
Body
Summary
The setting
github.copilot.chat.preferLongContext.enabledis currently enabled by default in VS Code Copilot Chat. This setting automatically pushes queries into extended context windows (up to 1M tokens) while obscuring manual context size selection from the user interface.I would like to flag significant concerns regarding this default configuration from an enterprise, cost governance, and UX transparency perspective.
All reactions