same
Same here. I really think it is unfair to charge this period of the last weeks.
Iām having issues - Cursor has been āplanning next stepsā for 2.5 hours and doesnāt respond when I stop it and ask it to try again.
Windows update recently? Or Google Drive sync issues?
Try to reboot your windows and try again, might help
And always remember that around 3PM CET all models will respond much slower, US is waking upā¦
Doesnt seem like anything has been fixed yet. I have had the same problem for the last week and can get it to work for a couple minutes and then it stops again. Any help would be greatly appreciated.
2 Likes
Some
macOS: 26.0.1
Cursor: Version: 2.1.50 (Universal)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.0.0
Request ID: eb372702-4173-419c-9b1c-c7afc4c513b7
ConnectError: [internal] 1116694002560:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40
at nsu.$streamAiConnect (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6409:406134)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:565:80832
at async Object.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6477:42602)
at async o (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2815:1269)
at async Promise.allSettled (index 0)
at async fHr.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2815:6519)
I am having this issue as well. No response from agents, network diagnostic just runs (except for Marketplace), indexing is stuck in a loop. Right now, Cursor is essentially down for me.
1 Like
Severe Norton Antivirus conflict with Cursor - connection failed during typescript builds
I tried all these:
Disabled HTTP/2 in Cursor
Fully reinstalled Cursor
Removed Cursor from Norton Program Control and reāallowed it
Added full folder exclusions for: Cursor program dir, Cursor roaming dir, node.js, npm cache dir, my entire project dir
Disabled all Cursor extensions
Verified that the issue only occurs when Norton is active
Verified that WSL builds do not trigger the issue
Any other suggestions?
I found an interesting workaroundāIām not sure how reliable it is, but it works perfectly in my case. The connection error often occurs in a new chat, especially when sending the first message. If you send āHiā in a new conversation, it responds instantly and then works without any issues afterward. Hope this helps you too! Version 2.0.77
What you need to do:
- Open a new chat
- Send āHiā
- The connection error should disappear
Unfortunately, Opening a new chat still doesnāt work. I think I may need to downgrade (currently v2.2.20) or use another IDE.
1 Like
I had this issue for the last 24 hours, tried new agents, restarting my computer, all the diagnosticsā¦. Nothingā¦ and it was solved by logging out and back into Cursor itself. 
Hope that helps someone else.
Can I ask what version do you use? I downgraded but the connections are still dropping intermittently. I will tried logging o it and see. Thank you.
The last two days (on 2.2.29 and 2.2.30) I have been getting a ton of āConnection Errorsā. Most recent is Request ID: fbf93cad-c6d4-4a00-bdc6-f892d3a20860
A conversation will go for a little while and then I am stopped dead.
They are not really connection errors. The Network Diagnostics have been 100% good every time I have checked, yet the conversation wonāt proceed no matter how many times I try.
If I start a new chat as Mark suggested, the new chat always works fine (at least at first) but if I try to resume the existing chat it never succeeds.
This makes Cursor pretty much unusable. Is there anything else (diagnostics etc.) I can offer that might help diagnose it?
Update: I just realized I had Early Access versions turned on.
Turned that off, and it installed from https://api2.cursor.sh/updates/api/update/win32-x64-user/cursor/2.2.20/6ad3f4f16b1670ddf3a56dd95af0eab9c0618f35c0c3e0934f2a4b7ffa42b955/stable
Still appears to have the same or very similar problem. Now Request ID: 300a2f32-2e61-4aed-9227-18f43e52d00c
ConnectError: [internal] Serialization error in aiserver.v1.StreamUnifiedChatRequestWithTools
at vscode-file://vscode-app/c:/Users/Vector/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12370:452123
And if I try again
Request ID: 755ba441-107c-439e-9de1-8b3db6503b0f
ConnectError: [internal] Serialization error in aiserver.v1.StreamUnifiedChatRequestWithTools
at vscode-file://vscode-app/c:/Users/Vector/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12370:452123
Not sure if you were referencing me, but Iām guessing possibly since it was right after my commentā¦ Hereās what Iām on from āAbout Cursorā
Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0
Update: Downgrading to 2.1.50 appears to fix it.
I am assuming my issue is the same as this:
And this: Planning next moves stuck
(further assuming these two are the same as each other)
I too am getting this error suddenly.
Request ID: 30c3fb93-c687-490d-95c7-185e95341f99
ConnectError: [internal] Serialization error in aiserver.v1.StreamUnifiedChatRequestWithTools
at vscode-file://vscode-app/c:/Users/{redacted}/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12375:452121
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.