Agent stuck on "…" and never reaches "Planning next moves" (network issue)

[cutalion (Alexander)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Sometimes the agent prints “…” and never proceeds to the “Planning next moves” step. I have to use the “Developer > Reload Window” command or close and reopen the app. After a reload/restart it just works.

I almost got used to it, but now it asks me to re-log in afterward, which is annoying (yes, even more than just reloading the window a few times a day).

This has been happening for a long time—maybe since 1.2 or earlier. I’m not sure when it started, but I don’t think it was happening in March/April.

While I was writing this post, it finally became unstuck with a network error (unfortunately, I closed the message and didn’t copy the request ID). I clicked “Try again,” and it worked. I ran network diagnostics—all green.

I checked the developer console—there are only network errors (timeouts). So it seems like a network issue, but I’m not sure it’s on my side, because it happens almost every day in various environments and locations: home Wi-Fi, mobile networks, with VPN (even more frequently), without VPN, and at my parents’ home.

Then I sent a simple “test” message to the agent just to check, and it got stuck. While it was stuck, I ran network diagnostics and that also got stuck (see attachment). I checked my internet connection—everything was fine.

This form doesn’t allow attach several files, I’ll add more screens in the thread.

Request info for the “test” request:

Request ID: 4211e82d-39d4-428e-90d8-3030447cf075
ConnectError: [unavailable] read ETIMEDOUT
    at wyl.$streamAiConnect (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4910:338871)
    at async vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:580:389069
    at async Omn.toolWrappedStream (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:3225:20560)
    at async w1s (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:580:411695)
    at async HR.handleStreamComposer (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:1450:993)
    at async Fzs.streamResponse (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:5494:24672)
    at async fjs.<anonymous> (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:5571:7351)
    at async njs.<anonymous> (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:5564:616)
    at async rjs.<anonymous> (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:5567:10365)
    at async ljs.<anonymous> (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:5567:26356)
    at async JWe.<anonymous> (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:3225:30825)
    at async see.processCodeBlocks (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:1501:3462)
    at async $re.submitChatMaybeAbortCurrent (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4303:6006)
    at async Fc (vscode-file://vscode-app/tmp/.mount_cursorAyZ4yZ/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4761:74142)

Steps to Reproduce

I don’t know, it just randomly happens.

Screenshots / Screen Recordings

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.26
VSCode Version: 1.99.3
Commit: 6af2d906e8ca91654dd7c4224a73ef17900ad730
Date: 2025-09-16T17:12:31.697Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-79-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

[cutalion (Alexander)]

I’m not sure what’s happening. It times out after 15 minutes, but when I reload the window, it works immediately, only asks to login now.

[cutalion (Alexander)]

I found another workaround besides reloading the window: stop the agent, switch compatibility mode from HTTP/2 to HTTP/1.1, and resend the message. It works, and I can switch back to HTTP/2 until it gets stuck again.

[Calfur (Robin Nater)]

I got the same issue since multiple weeks. Quite annoying.

I have a MacBook Pro M4 with the latest version of Cursor.

Maybe it’s related to an unstable network connection, but in my opinion the time until it times out and a retry option is shown is way to long (feels like > 30s). The retry always works instantly.