Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I am unable to open multiple dev containers at once through cursor, but this is something I was able to do in VSCode.
Steps to Reproduce
I normally develop entirely through a remote host with the Remote SSH plugin.
On this remote host, I have two different running containers.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
abcdefghijkl 111111111111 "/bin/bash -c 'echo …" 31 minutes ago Up 31 minutes debug-0
mnopqrstuvwx 111111111111 "/bin/bash -c 'echo …" 31 minutes ago Up 31 minutes debug-1
When I start a dev container for the first one, it works completely fine as expected:
Remote Explorer -> Dev Containers -> Other Containers -> debug-0 -> Attach in a New Window
However, when I want to open up a second dev container through the same steps, a number of different issues occur:
Remote Explorer -> Dev Containers -> Other Containers -> debug-1 -> Attach in a New Window
Example 1:
Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)
2025-10-16 19:06:11.700 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=142472][spawn] options: {"port":40833,"hostname":"127.0.0.1"}
2025-10-16 19:06:11.786 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=142472][stderr]: client error Error: connect ECONNREFUSED 127.0.0.1:40833
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1611:16)
2025-10-16 19:06:11.800 [info] [tunnel-forwarding] stderr: node:events:496
throw er; // Unhandled 'error' event
^
Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:161:15)
at writeGeneric (node:internal/stream_base_commons:152:3)
at Socket._writeGeneric (node:net:958:11)
at Socket._write (node:net:970:8)
at writeOrBuffer (node:internal/streams/writable:572:12)
at _write (node:internal/streams/writable:501:10)
at Writable.write (node:internal/streams/writable:510:10)
at Socket.ondata (node:internal/streams/readable:1009:22)
at Socket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:561:12)
Emitted 'error' event on Socket instance at:
at Socket.onerror (node:internal/streams/readable:1028:14)
at Socket.emit (node:events:518:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -32,
code: 'EPIPE',
syscall: 'write'
}
Node.js v20.18.2
2025-10-16 19:06:11.802 [info] Forwarder process exited with status 1, disposing of local tunnel
2025-10-16 19:06:11.802 [info] Stopping forwarder process
Example 2:
- For the dev container #2, I can choose to reinstall the cursor remote server and reload the window, and sometimes this does work, HOWEVER, then dev container #1 breaks and is in reloading state
Expected Behavior
I expect to be able to open both dev containers concurrently without them affecting each other
Operating System
MacOS
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.7.46 (Universal)
VSCode Version: 1.99.3
Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580
Date: 2025-10-14T01:21:46.830Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
Does this stop you from using Cursor
No - Cursor works, but with this issue