Planning next moves stuck

Support Bug Reports
168

Checked out, still having the issue.

169

Yes, it started working yesterday without me making any changes.

However it stopped working again when I came back this morning.

170

I have noticed that this happens a lot lately after updates after 1.6, meaning all updates after 1.7 and 2.0 becomes slow, or stuck on planning, and sometimes it runs the plan, and then half way in the plan, it simply gets stuck, not continuing.

I have tried with and without extensions, same on both.
It happens more on HTTP/2 than on HTTP/1.1
But both are a little slow sometimes, why doesn’t cursor auto detect the best HTTP version that works, rather than us having to manually choose?

Version: 2.1.0-pre.19.patch.0 (user setup)
VSCode Version: 1.99.3
Commit: a45ec7a1e9bd853a5b22e73114c195dcd0d68370
Date: 2025-11-09T08:15:46.581Z
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.26200

171

i have the same problem please check,
e9ec4003-2364-4022-8aa4-f50ee0ac6a42

172

Same here. This window has shown up 5 times in one hour. I hate this

obrazek
obrazek831×292 10.5 KB

173

Same here. Cursor is not working AT ALL. Have tried everything in the Forum threads. Will cancel my subscription now.

174

This is also happening to me, including on 2.0.75. For me, the issue isn’t so much the occasional connection timeout (which is annoying), but it’s that I get two options when the connection times out: (1) “Resume”, which sends the model into a seemingly-infinite “Planning next moves” state, which I can only get out of by starting a new chat and losing all context halfway through some action. Or (2) “Try Again” which will forget a ton of work and possibly time out again.

So, pretty much my chats last until I hit an inevitable connection error, and then I have to figure out how to avoid losing as much as possible. There is also some cost incurred due to loss of cache, context, and work, while potentially needing to re-prompt.

Note: I’ve disabled HTTP 2, which makes connection timeouts less frequent, but they still happen often enough, and my Internet connection isn’t particularly bad.

Edit: Request ID: c4b5b738-8b2b-47d3-8351-db15fe594005 … it seems to happen most often when running / fixing tests, which is doubly annoying because it’s usually close to the end of work and leaves things half working

175

Replying to myself. These are the console contents when I try to continue the session after a timeout error:

workbench.desktop.main.js:5606 [transport] Message serialization error in stream Error: invalid int 32: 4294967295
at u6n (workbench.desktop.main.js:441:32634)
at N2a.int32 (workbench.desktop.main.js:442:12763)
at uMt (workbench.desktop.main.js:442:19797)
at B2a (workbench.desktop.main.js:442:18900)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at ssi.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18998)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at Iti.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18998)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at lli.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18980)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at sli.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18980)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at Pai.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18998)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at sai.toBinary (workbench.desktop.main.js:441:34677)
at workbench.desktop.main.js:4989:396402 {arch: ‘x64’, platform: ‘win32’, channel: ‘stable’, client_version: ‘2.0.75’, service: ‘aiserver.v1.ChatService’, …}
error @ workbench.desktop.main.js:5606
(anonymous) @ workbench.desktop.main.js:4989
await in (anonymous)
$streamAiConnect @ workbench.desktop.main.js:4989
(anonymous) @ workbench.desktop.main.js:4989
GYs @ workbench.desktop.main.js:52
cH @ workbench.desktop.main.js:52
stream @ workbench.desktop.main.js:4989
(anonymous) @ workbench.desktop.main.js:590
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:2749
await in submitChatMaybeAbortCurrent
(anonymous) @ workbench.desktop.main.js:52
GYs @ workbench.desktop.main.js:52
qMd @ workbench.desktop.main.js:52
n.value @ workbench.desktop.main.js:52
Un @ workbench.desktop.main.js:4839
await in Un
onSubmit @ workbench.desktop.main.js:4839
Oe @ workbench.desktop.main.js:4700
onSubmit @ workbench.desktop.main.js:4700
handleSubmit @ workbench.desktop.main.js:4696
(anonymous) @ workbench.desktop.main.js:4696
FXa @ workbench.desktop.main.js:444
(anonymous) @ workbench.desktop.main.js:444
BXa @ workbench.desktop.main.js:444
hY @ workbench.desktop.main.js:444
update @ workbench.desktop.main.js:446
FXa @ workbench.desktop.main.js:444
Nc @ workbench.desktop.main.js:444
hWd @ workbench.desktop.main.js:444
(anonymous) @ workbench.desktop.main.js:444
workbench.desktop.main.js:55 ERR [internal] Serialization error in aiserver.v1.StreamUnifiedChatRequestWithTools: ConnectError: [internal] Serialization error in aiserver.v1.StreamUnifiedChatRequestWithTools
at vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4989:396431 ConnectError: [internal] Serialization error in aiserver.v1.StreamUnifiedChatRequestWithTools
at workbench.desktop.main.js:4989:396431Caused by: Error: invalid int 32: 4294967295
at u6n (workbench.desktop.main.js:441:32634)
at N2a.int32 (workbench.desktop.main.js:442:12763)
at uMt (workbench.desktop.main.js:442:19797)
at B2a (workbench.desktop.main.js:442:18900)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at ssi.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18998)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at Iti.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18998)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at lli.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18980)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at sli.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18980)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at Pai.toBinary (workbench.desktop.main.js:441:34677)
at U2a (workbench.desktop.main.js:442:19718)
at B2a (workbench.desktop.main.js:442:18998)
at Object.writeMessage (workbench.desktop.main.js:442:16664)
at sai.toBinary (workbench.desktop.main.js:441:34677)
at workbench.desktop.main.js:4989:396402
error @ workbench.desktop.main.js:55
error @ workbench.desktop.main.js:55
error @ workbench.desktop.main.js:7455
handleUnexpectedError @ workbench.desktop.main.js:7452
(anonymous) @ workbench.desktop.main.js:7452
onUnexpectedError @ workbench.desktop.main.js:27
Pa @ workbench.desktop.main.js:22
(anonymous) @ workbench.desktop.main.js:7452

176

@here I’m sure there is a better solution but I just re-installed the 1.7 version of cursor here:

I was having the same issue after updating to 2.0.
Would love to know a workaround for 2.0 but quick fix is just to install 1.7.

177

There is only one solution. Revert back to 1.7

178

I reverted to 2.0

It also reply smoothly. But it stuck on 2.1

179

Looks like it works for now. Here are request IDs which got a successful response: 41f8c9df-96b2-4fe6-9f90-2095be10e05c and bdaf9b71-7a81-4e79-bf55-a16c81bef526

180

Same problem still. Cursor is currently unusable. Incredibly frustrating.

Version: 2.1.39
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.8.0-87-generic

181

Exact same issue, had it for three straight days now, cursor is completely broken and unusable. Starting to look for different options now as the support seem to be doing nothing, no notice or anything. I gave them some benefit of the doubt previously but my patience is running thin now after 3 days of nothing. Need alternatives, Anti-gravity?

182

No 5 days and still completely unusable!

183

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Auto mode stuck forever on ‘Planning next moves’
Other models work, but I dont want to burn through my fast requests.

Steps to Reproduce

Just use auto mode.

Expected Behavior

Should respond and work.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.39 (user setup)
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
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

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

184

I’ve had this happen repeatedly over the past 5 days. I’m on windows 11 25h2 (on a 2025 asus flow z13 amd cpu laptop), running cursor 2.1.39, in agent mode, using gemini 3 or opus 4.5. The codebase it’s working on is an ssh’d directory on an arch linux box right beside this machine, and thanks to .cursorignore, it’s only indexing about 200 files. Here’s the list of things I’ve tried over the past 5 days that haven’t worked (haven’t worked as in - I create a new agent, say hello, and it says “planning next moves” forever):

  • the regedit gpu hack above

  • uninstalling and re-installing the cursor.com ssh plugin

  • deleting the codebase index and then having it regenerate it

  • closing the program, deleting all known cursor cache folders, then starting it again, here’s my powershell script to delete them all:

    Cursor Cache Cleanup Script

    Safely deletes Cursor cache/state folders

    $paths = @(
    “$env:APPDATA\Cursor\User\globalStorage”,
    “$env:APPDATA\Cursor\Cache”,
    “$env:LOCALAPPDATA\Cursor\User”,
    “$env:LOCALAPPDATA\Cursor\Cache”,
    “$env:LOCALAPPDATA\Cursor\Code Cache”,
    “$env:LOCALAPPDATA\Cursor\GPUCache”,
    “$env:LOCALAPPDATA\Cursor\blob_storage”,
    “$env:LOCALAPPDATA\Cursor\Crashpad”
    )

    Write-Host “=== Cursor Cache Cleanup ===`n”

    foreach ($path in $paths) {
    if (Test-Path $path) {
    try {
    Write-Host “Deleting: $path”
    Remove-Item -Recurse -Force -ErrorAction Stop $path
    }
    catch {
    Write-Warning “Failed to delete: $path — $($_.Exception.Message)”
    }
    }
    else {
    Write-Host “Not found (skipped): $path”
    }
    }

    Write-Host “`nDone! You can now restart Cursor.”

The one thing that DOES work however is uninstalling cursor, then running this powershell script that deletes every single file left over by cursor after the uninstall completes, making the install process be like I’m installing it for the first time (when I do this, I’ve gotten about 48 total hours of work done before it starts slowing down and eventually no longer responding)

==========================================

CURSOR IDE DEEP CLEANUP SCRIPT

==========================================

Write-Host “Starting aggressive cleanup of Cursor IDE…” -ForegroundColor Cyan

1. KILL RUNNING PROCESSES

------------------------------------------

Write-Host “Step 1: Terminating any lingering Cursor processes…” -ForegroundColor Yellow
$processes = Get-Process | Where-Object { $_.ProcessName -like “cursor” }
if ($processes) {
$processes | Stop-Process -Force
Write-Host " - Terminated $($processes.Count) background processes." -ForegroundColor Green
} else {
Write-Host " - No active Cursor processes found." -ForegroundColor Gray
}

2. DEFINE FOLDERS TO DELETE

------------------------------------------

Cursor stores data in Roaming (Configs), Local (Cache/Updater), and UserProfile (Extensions)

$folders = @(
“$env:APPDATA\Cursor”, # Main Config & storage
“$env:LOCALAPPDATA\Cursor”, # Local cache
“$env:LOCALAPPDATA\cursor-updater”, # Updater files
“$env:LOCALAPPDATA\Programs\cursor”, # Installation directory (if user install)
“$env:USERPROFILE.cursor”, # Extensions and server binaries
“$env:USERPROFILE.cursor-tutor” # Tutor cache (if exists)
)

Write-Host “`nStep 2: Removing directories…” -ForegroundColor Yellow
foreach ($folder in $folders) {
if (Test-Path $folder) {
try {
Remove-Item -Path $folder -Recurse -Force -ErrorAction Stop
Write-Host " - Deleted: $folder" -ForegroundColor Green
} catch {
Write-Host " ! Failed to delete: $folder (Check permissions or if file is open)" -ForegroundColor Red
}
} else {
Write-Host " - Not found (Clean): $folder" -ForegroundColor DarkGray
}
}

3. CLEAN REGISTRY KEYS

------------------------------------------

Write-Host “`nStep 3: Cleaning Registry Keys…” -ForegroundColor Yellow
$registryKeys = @(
“HKCU:\Software\Cursor”,
“HKCU:\Software\CursorAI”,
“HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\Cursor”,
“HKCU:\Software\Classes\cursor” # Protocol handlers
)

foreach ($key in $registryKeys) {
if (Test-Path $key) {
try {
Remove-Item -Path $key -Recurse -Force -ErrorAction Stop
Write-Host " - Removed Registry Key: $key" -ForegroundColor Green
} catch {
Write-Host " ! Error removing key: $key" -ForegroundColor Red
}
} else {
Write-Host " - Key not found: $key" -ForegroundColor DarkGray
}
}

4. FINAL VERIFICATION

------------------------------------------

Write-Host “`n------------------------------------------”
Write-Host “Cleanup Complete.” -ForegroundColor Cyan
Write-Host “You can now perform a fresh install of Cursor.”
Write-Host “Download it fresh from cursor.com to ensure no old installers are used.”
Write-Host “------------------------------------------”

185

It wasn’t working first, then I just waited and read around, tried it on my phone’s hotspot (didn’t fix anything), then turned my uni’s VPN off, and it worked again all of a sudden ¯\_(ツ)_/¯

No idea if that was the reason it helped, it’s quite a mystery to me how it got fixed, because now Cursor works with and without VPN on all networks. Windows 11 24H2.26100.7171 + Cursor 2.1.39.

Random thought: could it be OneDrive messing with my files? It was uploading lots of files while I was debugging this.

186

Same issue for me:

Macbook Pro

Version: 2.1.46 (Universal)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
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.1.0

187

Same, what are the suggestions to fix this?
and the steps to pls.
Diagnostics are all good, restarted pc, router, everything…
I installed an update today, still the same.
Version: 2.1.47 (user setup)
VSCode Version: 1.105.1
Commit: 2d3ce3499c15efd55b6b8538ea255eb7ba4266b0
Date: 2025-12-04T02:31:50.567Z
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