Describe the Bug
I pretty frequently get the following error when running cursor --install-extension whatever.vsix from within Cursor while remote (ssh) connected to a cursor host server.
cursor --install-extension mwg-verilog-helpers-0.0.70.vsix
Unable to connect to VS Code server: Error in request.
Error: connect ENOENT /run/user/1000/vscode-ipc-2fe3bd74-c476-4f7e-a5ca-3311a9a4e841.sock
at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1611:16) {
errno: -2,
code: 'ENOENT',
syscall: 'connect',
address: '/run/user/1000/vscode-ipc-2fe3bd74-c476-4f7e-a5ca-3311a9a4e841.sock'
}
The only solution I have found so far is to reboot the ssh host machine, which forces a restart of cursor-server, but this is a hassle.
When this happens, I check whether the IPC socket exists or not. What I find is that there are a bunch of vscode IPC sockets, but none have this name:
# results from immediately after getting error show above
mwg@metal:~/mwg-verilog-helpers$ ls -la /run/user/1000/vscode-ipc*
srwxrwxr-x 1 mwg mwg 0 Jun 17 12:27 /run/user/1000/vscode-ipc-01df9ad6-98c1-4de1-a1c9-a74ab8021a6d.sock
srwxrwxr-x 1 mwg mwg 0 Jun 18 16:57 /run/user/1000/vscode-ipc-0ac7508a-51b6-4515-87ed-c52cbd0a63a9.sock
srwxrwxr-x 1 mwg mwg 0 Jun 18 16:57 /run/user/1000/vscode-ipc-1155dcae-3ae2-474c-9ce8-ab7e7ad9cd9b.sock
srwxrwxr-x 1 mwg mwg 0 Jun 16 13:23 /run/user/1000/vscode-ipc-170c0f36-dca8-4c7a-aee1-5ac6e0e28cdc.sock
srwxrwxr-x 1 mwg mwg 0 Jun 18 16:56 /run/user/1000/vscode-ipc-48e0bd10-9542-4524-b25f-565ec7c945e0.sock
srwxrwxr-x 1 mwg mwg 0 Jun 16 13:23 /run/user/1000/vscode-ipc-4b26658f-e44a-43de-96ae-89452e0ada8c.sock
srwxrwxr-x 1 mwg mwg 0 Jun 16 13:23 /run/user/1000/vscode-ipc-508ac536-e4b6-40bf-8f23-40aa3805d7ad.sock
srwxrwxr-x 1 mwg mwg 0 Jun 17 12:27 /run/user/1000/vscode-ipc-56e5db1b-002a-4f03-8253-2347c3e0b5b9.sock
srwxrwxr-x 1 mwg mwg 0 Jun 18 16:57 /run/user/1000/vscode-ipc-5cacc1a9-3518-4eb7-8a7c-533391ce1e8c.sock
srwxrwxr-x 1 mwg mwg 0 Jun 16 07:31 /run/user/1000/vscode-ipc-9330430b-ef0a-48b2-b60d-7ce403281521.sock
srwxrwxr-x 1 mwg mwg 0 Jun 17 01:05 /run/user/1000/vscode-ipc-a3f88fe4-32e9-4348-8582-5b48e450da6b.sock
srwxrwxr-x 1 mwg mwg 0 Jun 17 01:03 /run/user/1000/vscode-ipc-c79b2443-409d-4d8c-9394-e18481f40d2e.sock
srwxrwxr-x 1 mwg mwg 0 Jun 16 07:31 /run/user/1000/vscode-ipc-c91e4d9a-b42a-4594-a663-d64718dc99ee.sock
srwxrwxr-x 1 mwg mwg 0 Jun 16 07:31 /run/user/1000/vscode-ipc-d47b4f51-5729-42b3-ac69-41ea66c00557.sock
Note: I 
Cursor and therefore I am only using Cursor, not native VSCode or any other VSCode derivative. So, I don’t think this is some conflict between IPC sockets from different versions of VSCode.
Note also: native VSCode users have report this problem in the past (e.g., this issue but it doesn’t seem like it’s happening recently. I think it may have been fixed in upstream back around 2022 or 2023?
Open to any workarounds in the meantime! Thank you for Cursor it is 
and keeps getting better.
Steps to Reproduce
Well, it happens sporadically, but basically if you just leave Cursor Desktop IDE remotely logged into some workspace on an ssh cursor-server instance for a few days, and periodically run cursor --install-extension <your-vsix-file>.vsix in the cursor terminal window in the IDE, it will happen after a while.
Expected Behavior
I expect cursor to find the current IPC socket correctly every time and not produce the ENOENT error.
Screenshots / Screen Recordings
Operating System
MacOS
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.1.3
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:35:49.230Z (3 days ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
Does this stop you from using Cursor
No - Cursor works, but with this issue
