I’m not seeing an outage like yesterday, but it is definitely much slower than normal. I have it set to Auto for a replacement of a Logo and it has been running for 40 minutes so far.
Steps to Reproduce
Application is node / react
Replace Logo with a new logo, new file is provided in chat
Model is set to Auto
Expected Behavior
Response in a minutes not 40 minutes and no response.
Hey @George_Broadbent, thanks for the report, and sorry about the wait.
Looking at what we can see on our side, the request from your chat never actually made it to our servers, so this isn’t Auto being slow. Your account and usage look fine. Cursor updated to 3.21.9 on your machine today, and there’s a known issue on that version where an Agent message in the IDE window can get stuck on “Taking longer than expected…” before it’s ever sent. We’re tracking it, and I’ve added your report.
Two things that should get you unblocked right away:
Press Ctrl+Shift+P, type “Open Agents Window” and press Enter. Run the logo replacement from there (Auto is fine). The Agents Window isn’t affected by this, and from what we can see it’s already working on your machine.
If you’d rather stay in the IDE window: click Stop on the stuck message, press Ctrl+Shift+P, run “Developer: Reload Window”, then send the message again in a new chat. On 3.21.9 the stall is per message, so a retry often goes through.