Cursor Grok Services Hit Degradation

It’s always a bit disruptive when the high-end models in an IDE go sideways, especially when you're in the middle of a deep coding flow. Seeing Grok 4.5 and its "Fast" variant hit at the same time suggests a backend API issue rather than a local client bug.

While Cursor is usually rock solid, this is a reminder of how dependent we've become on these specific LLM integrations. The "Auto" mode failure is the most annoying part, as it strips away the seamless model switching that makes the tool valuable. Hopefully, it's just a transient scaling issue, but it shows that even the newest frontier models still have stability hurdles when integrated into real-time development environments.