Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
When attempting to “Reopen in Container” within a project hosted in WSL, the Dev Container build process proceeds through the image creation and container startup phases. However, after the container is successfully started, the process hangs. The UI does not transition into the containerized environment, and no further setup (like installing the VS Code server extensions) occurs.
Steps to Reproduce
- Open a project located in a WSL partition using Cursor.
- Run the command “Dev Containers: Reopen in Container”.
- Observe the Dev Container terminal. The process reaches the “container started” event but fails to connect the IDE to the running container.
Expected Behavior
After the container starts, Cursor should connect to the container, install the necessary server-side components, and refresh the workspace window inside the container environment.
Fyi: It works fine with the current VSCode Version.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.3.34 (user setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200
Does this stop you from using Cursor
Yes - Cursor is unusable