WARNING: SSMS Copilot Can Unknowingly Burn Up Your Premium Requests! #187767
Replies: 2 comments
-
|
💬 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.
-
|
It's a known bug. The suggestion is to update to latest SSMS version. Happened to me too. |
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
General
Body
I was just using SSMS Copilot to help optimize a TSQL query using Claude Sonnet 4.6. It got stuck during answering a question (or so I thought), then an hour or so later I noticed that my pro usage meter had surged from about 40% to 75%. It somehow had used up 500+ premium requests without me knowing! What gives? This has never happened using Visual Studio or VS Code.
Beta Was this translation helpful? Give feedback.
All reactions