Stops working again - Connection Error

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Response is supper laggy ,

After showing “Planning next moves”, stuck for 1min and then showed up

Connection Failed

Steps to Reproduce

Run any agent and see

Expected Behavior

Run smoothly

Screenshots / Screen Recordings

Screenshot 2025-11-26 at 11.50.59 AM.png
Screenshot 2025-11-26 at 11.50.59 AM.png1494×244 9.59 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.36 (Universal)
VSCode Version: 1.105.1
Commit: 9cd7c8b6cebcbccc1242df211dee45a4b6fe15e0
Date: 2025-11-26T03:43:48.079Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin x64 23.4.0

For AI issues: which model did you use?

Component, Auto

Does this stop you from using Cursor

Yes - Cursor is unusable

Can’t create new chats
2

Same it’s happening to me since update. Version: 2.1.36

3

Also bricked here. It appears that the URL in question does not have a Visual Studio build available:

[14:00:00.932] > wget download failed

> https://update.code.visualstudio.com/commit:9cd7c8b6cebcbccc1242df211dee45a4b6fe

> 15e0/server-linux-x64/stable: 2025-11-26 14:00:00 ERROR 404: Not Found.

5

Hey, thanks for the report. Several users are experiencing Agent connection issues after updating to v2.1.36.

First, try testing without extensions:

Run this in your terminal:
cursor --disable-extensions

Then test the Agent in the new window. A recently solved case had similar symptoms (stuck on “Planning next moves” → timeout) and was caused by extensions, even though network diagnostics suggested otherwise.

If that doesn’t help, please share:

  • Console errors: Help > Toggle Developer Tools > Console tab (screenshot any errors)
  • Network diagnostics: Cursor Settings > Network > Run Diagnostics
  • Request ID: Chat context menu (top right) > Copy Request ID after the error occurs
  • Are you using remote SSH connections or working locally?

@Newty - Your 404 error seems like a separate remote SSH issue. Could you clarify if you’re trying to connect to a remote server?

Let me know what you find.

6

It looks like Microsoft resolved their binary issue. Might have been ephemeral. I connected this morning. Thanks!