Dev Container hangs on "Reopen in container" via SSH

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When running “Reopen in container,” the connection hangs indefinitely on the loading screen and never completes.

Steps to Reproduce

  1. Open Cursor on the host machine
  2. Press Ctrl+P and run “Connect Current Window to Host” to SSH into a remote Linux machine
  3. Open a folder that contains a devcontainer configuration
  4. Run “Reopen in Container”
  5. The loading screen appears and hangs indefinitely

Expected Behavior

Cursor should successfully install the Cursor Server inside the container and attach to it, completing the Dev Container setup without hanging.

Screenshots / Screen Recordings

IMG_1999.png
IMG_1999.png219×142 2.07 KB

Operating System

Windows 10/11
Linux

Version Information

Version: 3.0.13 (user setup)
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.22631Connecting the dev container via SSH from Windows

Additional Information

Devcontainer Extension: 1.0.32

The following errors appear in the Developer Tools console:

Failed to install Cursor server: The "path" argument must be of type string. Received undefined
ERR [LocalProcess1][resolveAuthority(dev-container,1)][3868ms] returned an error {code: 'NoResolverFound', message: 'No remote extension installed to resolve ssh-remote.'}

repeatedly running “Reload Window” via Ctrl+P may eventually allow the connection to succeed, but this is not reliable and requires multiple attempts.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

I have the same problem.

Interestingly with version 3.0.16.
Downgrading to version 3.0.13 solved it temporarily.
3.0.13 successfully connects about 1 in 4 times.
3.0.16 is completely unusable.

The GUI hangs on connecting to the container at a point where the “Output”-Panel is not even available yet, making it impossible to view any logs.

6

Hey, I see you already ran into this in a previous thread. It’s the same known bug with .gitconfig path resolution in the Dev Containers extension over SSH. I won’t repeat the workaround since I know you’ve tried everything already.

@LazyOwl, thanks for the info about the regression in 3.0.16. That’s a helpful signal, I’ll pass it to the team. The fact that the Output panel isn’t even available is also a useful detail.

The main discussion and tracking for this bug is here: Failed to install Cursor server: The "path" argument must be of type string. Received undefined

I’m closing this thread as a duplicate. Please follow that thread to get updates when there’s news. The team is aware of the issue, but there’s no ETA yet. Your reports help with prioritization.

7

A post was merged into an existing topic: Failed to install Cursor server: The “path” argument must be of type string. Received undefined