Connection Failed - Cursor Stops accepting Commands

@condor Yes. The issue still exists on latest 1.6 version. I just update and try.

Version: 1.6.26 (system setup)
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: Windows_NT x64 10.0.19045

@1821746019 Please check Settings > Network > Run Diagnostic and report any errors shown there.

My network is fine, but the UI is not…

It’s a path resolving issue between window host and linux remote machine, not the network.

I think I described the same (or a very similar) issue here: Agent stuck on "…" and never reaches "Planning next moves" (network issue)

I’ve found a quick workaround: when the agent hangs, switch compatibility mode to HTTP/1.1, then resend. I switch back to HTTP/2 afterward.

Leaving this here in case it helps anyone else.

2 Likes

@1821746019 are you using Remote SSH or similar way to connect Windows with Linux machine? this could be the issue

1 Like

It’s a path resolving issue between window host and linux remote machine, not the network.

Yes. I use Remote Tunnel to connect Windows with Linux machine. The issue didn’t exist in v1.3. I am sure that a regression was introduced in Cursor v1.4.
@condor

Concur this is still occuring - as @Erik_Z noted above - I can reliably do this by forcing the app to do work on code that is outside of the current project’s folder path - i.e. elsewhere on the system. That will cause it to submit the same console errors as @1821746019 noted:

If I return to the prior chat comment I made, and direct the app to NOT address code outside of the current project path, IO can remedy the situation, tho of course then the model loses the context of what it just wrote (whether I revert code or not, it will resolve the issue and allow me to continue the conversation).

Please, look to @Erik_Z ‘s notes and fix :folded_hands:

– to confirm, this is when cursor on windows, and code/server is connected to remote linux via ssh.

– to double check - if I remove the errant context bubbles for the files that show that they are using the “fakey backslash filepaths” (i.e. like \home\user\coding\example.py - that is outside the current project path) - if I remove those from the @context reference - then I can sometimes submit the next inquiry

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.