Cursor recently disappointed me for basic things

Bug Reports
1

Describe the Bug

Cursor recently disappointed me on basic things.

  1. the login with remote server gets disconnected quite often even with their recommended ssh. i do not have issue the vs code - which is quite stable.
  2. the account sign-out option is not available in the IDE setting after version 1.0. the signout and signin with new account on the online web-page does not affect the local IDE account.

Are you guys really taking your business seriously?

Steps to Reproduce

  1. for account management issue, you just try signout
  2. for the ssh disconnection issue, not easy to reproduce

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.0+ <<<<<<<<<<<<<<<<

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hi @czhang_ff, thanks for your post and sorry to hear about these issues.

Re: 1., what issue are you running into, and how frequently does this happen? Is it requiring you to reload the window frequently, or is it just failing to connect? It’d be helpful if you could share the logs from the “Remote - SSH” output window so I can take a look:

image
image1123×160 5.14 KB

Re: 2., you’ll need to use the sign out button in app. Attaching a screenshot.

image
image555×960 18.4 KB

4

Thanks for following up!

  1. It looks like the new version changed the location of the sign-out option, and I completely missed it — appreciate you pointing that out!
  2. Regarding the connection dropping issue: it’s currently back to normal, though I’m not exactly sure which step fixed it. For documentation purposes, here’s a summary of what happened:

a. SSH was frequently disconnecting, and I noticed messages indicating connection drops.
b. I searched online and found an old post suggesting a fix. I followed the advice and replaced the SSH binary with the one you recommended.
c. The annoying warning messages disappeared after that, but the actual disconnections still occurred — I could feel it when the Cursor terminal froze.
d. I consistently compared the experience with VS Code (on the same setup), which never had this issue.
e. Then came the logout issue. I tried various things, and at one point I couldn’t log into the remote server from either VS Code or Cursor. Based on ChatGPT’s suggestion, I deleted some related files.
f. After that, I logged in again using Cursor v1.0 — and everything started working smoothly. The disconnection issue also vanished.

Thanks again for your support!

6

Ok. i withdraw my statement that “it gets back normal”.
Actually the disconnection gets less frequently now. it has less impact to my work.

2025-06-17 11:54:15.992 [info] [forwarding][multiplex][127.0.0.1:34359 → 127.0.0.1:36221 → 127.0.0.1:34617][e8b5c368-935d-45a1-ba0d-a86dbdb21ac6] socks forwarding established

2025-06-17 11:54:16.032 [info] [command][63843a07-75ae-416b-b8a5-3bf46638a638] Process exited with code 0

2025-06-17 11:54:16.032 [info] [command][63843a07-75ae-416b-b8a5-3bf46638a638] Socket close event received

2025-06-17 11:54:16.033 [info] [forwarding][multiplex][127.0.0.1:34359 → 127.0.0.1:36221 → 127.0.0.1:34617][e8b5c368-935d-45a1-ba0d-a86dbdb21ac6] socks connection closed

2025-06-17 11:54:16.070 [info] (ssh_tunnel) stderr: debug1: channel 4: free: direct-tcpip: listening port 36221 for 127.0.0.1 port 34617, connect from 127.0.0.1 port 60742 to 127.0.0.1 port 36221, nchannels 6

2025-06-17 11:55:16.627 [info] [remote-ssh] Pinging remote server on port 34359

2025-06-17 11:55:16.676 [info] [forwarding][multiplex][127.0.0.1:34359 → 127.0.0.1:34617][be111726-0fc6-460d-b1c7-f0695d224210] received connection request

2025-06-17 11:55:16.677 [info] [command][9da8b3a6-6740-489b-a1ec-6721d5a65a6d] Sending command request: {“command”:“echo”,“args”:[“1”],“env”:{},“token”:“3f18865b-a3e0-477b-805a-2f4a318a260b”,“id”:“9da8b3a6-6740-489b-a1ec-6721d5a65a6d”}

2025-06-17 11:55:16.687 [info] (ssh_tunnel) stderr: debug1: Connection to port 36221 forwarding to socks port 0 requested.

debug1: channel 4: new [dynamic-tcpip]

2025-06-17 11:55:16.851 [info] [forwarding][multiplex][127.0.0.1:34359 → 127.0.0.1:36221 → 127.0.0.1:34617][be111726-0fc6-460d-b1c7-f0695d224210] socks forwarding established

2025-06-17 11:55:16.899 [info] [command][9da8b3a6-6740-489b-a1ec-6721d5a65a6d] Process exited with code 0

2025-06-17 11:55:16.899 [info] [command][9da8b3a6-6740-489b-a1ec-6721d5a65a6d] Socket close event received

2025-06-17 11:55:16.900 [info] [forwarding][multiplex][127.0.0.1:34359 → 127.0.0.1:36221 → 127.0.0.1:34617][be111726-0fc6-460d-b1c7-f0695d224210] socks connection closed

2025-06-17 11:55:16.946 [info] (ssh_tunnel) stderr: debug1: channel 4: free: direct-tcpip: listening port 36221 for 127.0.0.1 port 34617, connect from 127.0.0.1 port 52402 to 127.0.0.1 port 36221, nchannels 6

2025-06-17 11:56:16.899 [info] [remote-ssh] Pinging remote server on port 34359

2025-06-17 11:56:16.900 [info] [forwarding][multiplex][127.0.0.1:34359 → 127.0.0.1:34617][40e03e65-d06f-4ff3-8cca-df2a573ae2a7] received connection request

2025-06-17 11:56:16.901 [info] [command][e0716fa8-291c-4773-a4fe-b4cb27d9bb7b] Sending command request: {“command”:“echo”,“args”:[“1”],“env”:{},“token”:“3f18865b-a3e0-477b-805a-2f4a318a260b”,“id”:“e0716fa8-291c-4773-a4fe-b4cb27d9bb7b”}

2025-06-17 11:56:16.901 [info] (ssh_tunnel) stderr: debug1: Connection to port 36221 forwarding to socks port 0 requested.

debug1: channel 4: new [dynamic-tcpip]

2025-06-17 11:56:16.950 [info] [forwarding][multiplex][127.0.0.1:34359 → 127.0.0.1:36221 → 127.0.0.1:34617][40e03e65-d06f-4ff3-8cca-df2a573ae2a7] socks forwarding established

2025-06-17 11:56:16.992 [info] [command][e0716fa8-291c-4773-a4fe-b4cb27d9bb7b] Process exited with code 0

2025-06-17 11:56:16.992 [info] [forwarding][multiplex][127.0.0.1:34359 → 127.0.0.1:36221 → 127.0.0.1:34617][40e03e65-d06f-4ff3-8cca-df2a573ae2a7] socks connection closed

2025-06-17 11:56:16.993 [info] [command][e0716fa8-291c-4773-a4fe-b4cb27d9bb7b] Socket close event received

2025-06-17 11:56:17.048 [info] (ssh_tunnel) stderr: debug1: channel 4: free: direct-tcpip: listening port 36221 for 127.0.0.1 port 34617, connect from 127.0.0.1 port 43760 to 127.0.0.1 port 36221, nchannels 6

8

Today situation became worse. The IDE notified ssh fully disconnected and asked for reload. At the same time, the VS code has no issue.

After disconnection iteration, i found Cursor or AI tools randomly deleted my core codes. I tried to use so-called checkpoint recovery. it did only partial recovery. I would expect Cussor gave a better explanation about this and how to avoid…

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

main 2025-06-18T15:17:40.916Z] Extension host with pid 116961 exited with code: 0, signal: unknown.
[main 2025-06-18T15:17:40.954Z] [UtilityProcess id: 2, type: fileWatcher, pid: 116558]: crashed with code 15 and reason ‘killed’
[main 2025-06-18T15:35:48.809Z] Extension host with pid 117071 exited with code: 134, signal: unknown.
[main 2025-06-18T15:35:48.810Z] [UtilityProcess id: 10, type: extensionHost, pid: 117071]: crashed with code 134 and reason ‘crashed’
[main 2025-06-18T15:35:52.047Z] [UtilityProcess id: 2, type: fileWatcher, pid: 117089]: crashed with code 15 and reason ‘killed’
[main 2025-06-18T15:35:57.025Z] Extension host with pid 117989 exited with code: 0, signal: unknown.
[main 2025-06-18T15:42:31.603Z] Extension host with pid 118008 exited with code: 134, signal: unknown.
[main 2025-06-18T15:42:31.604Z] [UtilityProcess id: 12, type: extensionHost, pid: 118008]: crashed with code 134 and reason ‘crashed’
(node:61734) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 closed listeners added to [BrowserWindow]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
[main 2025-06-18T15:42:38.597Z] Extension host with pid 118373 exited with code: 0, signal: unknown.
[main 2025-06-18T15:50:39.436Z] Extension host with pid 118393 exited with code: 134, signal: unknown.
[main 2025-06-18T15:50:39.437Z] [UtilityProcess id: 14, type: extensionHost, pid: 118393]: crashed with code 134 and reason ‘crashed’
[main 2025-06-18T15:50:46.715Z] Extension host with pid 118834 exited with code: 0, signal: unknown.
[main 2025-06-18T15:51:08.891Z] Extension host with pid 118853 exited with code: 134, signal: unknown.
[main 2025-06-18T15:51:08.891Z] [UtilityProcess id: 16, type: extensionHost, pid: 118853]: crashed with code 134 and reason ‘crashed’
(node:61734) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 vscode:disconnect listeners added to [IpcMainImpl]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
[main 2025-06-18T15:51:15.858Z] Extension host with pid 119052 exited with code: 0, signal: unknown.
[main 2025-06-18T15:52:28.589Z] Extension host with pid 119070 exited with code: 134, signal: unknown.
[main 2025-06-18T15:52:28.590Z] [UtilityProcess id: 18, type: extensionHost, pid: 119070]: crashed with code 134 and reason ‘crashed’
[main 2025-06-18T15:52:31.677Z] [UtilityProcess id: 2, type: fileWatcher, pid: 119094]: crashed with code 15 and reason ‘killed’
[main 2025-06-18T15:52:36.656Z] Extension host with pid 119216 exited with code: 0, signal: unknown.
[main 2025-06-18T15:54:26.589Z] Extension host with pid 119234 exited with code: 134, signal: unknown.
[main 2025-06-18T15:54:26.589Z] [UtilityProcess id: 20, type: extensionHost, pid: 119234]: crashed with code 134 and reason ‘crashed’
[main 2025-06-18T15:54:35.341Z] Extension host with pid 119351 exited with code: 0, signal: unknown.

10

Hi @czhang_ff, thank you for sharing this these logs.

Looks like there are two issues going on:

  1. Re: the SSH connection drops / forced window reloads, could you try adding ServerAliveInterval 30 and ServerAliveCountMax 5 to your SSH config file under the entry for this host? It’s unclear from the logs why the connection dropped, but would be helpful to know whether these flags help.

  2. Re: the checkpoint recovery, if agent runs a command to modify code, then checkpoint recovery may not work. I would also recommend git staging before running agent, so you can also restore from that.