Planning next moves stuck

Request ID: 8e965e06-dc80-4054-b97e-25d9d81c1991
ConnectError: [internal] 1151053735552: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)

Is there any kind of time horizon for the fix ?

I fixed it by rolling back to 2.0.11

You can all do the same by rolling back here.

I found the fix, roll back to. 20.11

It’s extremly slow!

Good! It works for me

1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have been trying to work with the chat window to generate code. Used Agent / Plan mode and switched across multiple LLMs from Claude-connet to haiku. Cleared index. Restarted the machine., But nothing seems to be working. It has happened once before with me in the past but it got resolved on its own the next day but today also it is just as slow. May I know some steps I can take to get it working as it was working before. It is stuck at Planning next moves for minutes..

Steps to Reproduce

Open a project. Give any instruction to the Agent window in any mode Agent / Ask / Plan

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

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 24.6.0

For AI issues: which model did you use?

Sonnet 4.5
Auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

Same issue with me, it took 5-10 minutes to response to even a simple message like “fix this color”. I don’t even use a lot of files to fill up the context. It often stuck at “Planning next moves” for supeerrrrr long. Many members in my team reported the same issue.

3 Likes

Same issues
Between 1h-8h AM - American time zone

2 Likes

same here :woman_raising_hand:t2:

same issue, please fix! @cursor team

I had the exact same bug for multiple days, and rolling back to. 20.11

Fixed it for me.

Unusable for me. It’s continually spinning whilst making an edit to a file (but fails to actually modify the file.)

Request id: 92578980-f396-410f-9a23-12324635d863

Spent at least 5 minutes making an edit to a single file before I cut it off.

No support at all, only the “we are working on it” bureaucratic lie, but they are still charging us for the subscription of this unusable thing.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I noticed that Cursor runs very slowly, for example, it often gets stuck on “Planning next moves.”

How can I investigate this?

Also with simple messages like ‘Hello’, it stuck on “Planning next moves.”

Cursor settings > Network > Run Diagnostic: All fine
Tried also to change different HTTP Compatibility Mode.

Steps to Reproduce

Just open cursor and prompt something.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.54
VSCode Version: 1.99.3
Commit: 7a31bffd467aa2d9adfda69076eb924e9062cb20
Date: 2025-11-03T22:40:44.657Z (17 hrs ago)
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

For AI issues: which model did you use?

Auto, and other models.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi @deanrie, I’ve been seeing the same issue since updating to 2.0 last week. Here’s an example request ID which is stuck: 1e767ab0-731c-4cd8-9bba-82349a0981e0

I also tried your empty-project suggestion. With an empty folder in Windows, the Agent responded immediately to a chat message. I also tried an empty folder in WSL, and again the Agent worked perfectly. Once I opened my project workspace, which is a large company-wide monorepo in WSL, the Agent got stuck on “planning next moves” again. Switching to HTTP/1.1 did not help.

Here’s my current version:

Version: 2.0.54 (user setup)
VSCode Version: 1.99.3
Commit: 7a31bffd467aa2d9adfda69076eb924e9062cb20
Date: 2025-11-03T22:40:44.657Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

Also FYI there’s another thread regarding this same issue: The Cursor IDE freezes at the "planning next moves" stage

1 Like

Did it work without you making any changes?

Request ID: 28216b9a-d25e-42ed-88fe-113b529e6bcb

Console error:

[Truncated]
workbench.desktop.main.js:55 ERR [aborted] Client network socket disconnected before secure TLS connection was established: ConnectError: [aborted] Client network socket disconnected before secure TLS connection was established
at t (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7337:400502)
at async Object.getDefaultModelNudgeData (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:587:348407)
at async Uzr.performDefaultModelRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7955:7722)
at async Promise.all (index 1)
at async lQn.withSemaphore (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1441:4800) ConnectError: [aborted] Client network socket disconnected before secure TLS connection was established
at t (workbench.desktop.main.js:7337:400502)
at async Object.getDefaultModelNudgeData (workbench.desktop.main.js:587:348407)
at async Uzr.performDefaultModelRequest (workbench.desktop.main.js:7955:7722)
at async Promise.all (index 1)
at async lQn.withSemaphore (workbench.desktop.main.js:1441:4800)
error @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 WARN ToolCallEventService: Tracked tool call end - toolu_01ByBsRUZ2VZG36TvGbrn3JU
warn @ workbench.desktop.main.js:55
workbench.desktop.main.js:5101 [composer] Failed to get complete AI response
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:5101
workbench.desktop.main.js:7952 [composer] Chat incomplete or aborted Object
_log @ workbench.desktop.main.js:7952
workbench.desktop.main.js:55 ERR [aborted] Client network socket disconnected before secure TLS connection was established: ConnectError: [aborted] Client network socket disconnected before secure TLS connection was established
at t (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7337:400502)
at async Object.getTeams (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:587:348407)
at async qdo.getTeams (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9773:35106)
at async qdo.refreshMembership (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9773:23037) ConnectError: [aborted] Client network socket disconnected before secure TLS connection was established
at t (workbench.desktop.main.js:7337:400502)
at async Object.getTeams (workbench.desktop.main.js:587:348407)
at async qdo.getTeams (workbench.desktop.main.js:9773:35106)
at async qdo.refreshMembership (workbench.desktop.main.js:9773:23037)
error @ workbench.desktop.main.js:55
error @ workbench.desktop.main.js:55
error @ workbench.desktop.main.js:9802
handleUnexpectedError @ workbench.desktop.main.js:9799
(anonymous) @ workbench.desktop.main.js:9799
onUnexpectedError @ workbench.desktop.main.js:27
ka @ workbench.desktop.main.js:22
(anonymous) @ workbench.desktop.main.js:9799

It happens in different scenario, mainly when I’m connected to a machine with SSH.

Extension MCP: yes, only github

Tried with the workarounds, nothing is working.

1 Like