Hey, thanks for the detailed report. This is part of an ongoing server-side degradation on the model provider side, and it’s currently impacting Composer 2.5, and Auto when steps route to it. The reason it gets stuck on “Planning next moves” is that the request reaches our servers, but the provider is slow to return the first token. The client shows that placeholder until anything starts streaming.
You’re right that the status page looks outdated. I’ve passed it to oncall to update status.cursor.com, a new wave is already active there.
Until the degradation settles down, here are the workarounds:
Switch to a non-Composer model, like GPT or the Claude family. They’re streaming normally right now.