Reopen in Dev Container stopped working

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Reopen in Dev Container fails with alert message “Cannot reconnect. Please reload the window.”

Steps to Reproduce

I have a project with multiple dev containers and os of today I can no longer connect to one of my dev containers. All other dev containers work as intended.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.39 (Universal)
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

Additional Information

2025-11-27 18:03:59.762 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=39974][spawn] options: {“port”:44365,“hostname”:“127.0.0.1”}

2025-11-27 18:03:59.829 [info] [devcontainer run-user-commands]: {“type”:“text”,“level”:3,“timestamp”:1764259439829,“text”:“@devcontainers/cli 0.75.0. Node.js v22.20.0. darwin 25.1.0 arm64.”}
2025-11-27 18:03:59.829 [info] [devcontainer run-user-commands]: {“type”:“start”,“level”:2,“timestamp”:1764259439829,“text”:“Run: docker buildx version”}
2025-11-27 18:03:59.867 [info] [tunnel-forwarding] stdout: forwarder: [handleClient][subprocess=39961][stderr]: Remote close

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report. The “Cannot reconnect” and “Remote close” issues in the logs might be related to the Dev Containers extension.

Quick checks:

  • Check the Anysphere Dev Containers extension version - update to 1.0.28 (Extensions > find Dev Containers > Check for Updates)
  • Check Docker Desktop version - if it’s 4.52.0, try updating to the latest or rolling back to 4.51.0
  • Try recreating the problematic container (docker rm + rebuild)
  • Clear the cache: delete the .cursor-server folder inside the container

Similar resolved threads:

Could you clarify: what versions of Docker Desktop and Dev Containers extension do you have installed? Let me know what happened after the checks.

4

Hey @deanrie , thanks so much for getting back to me. I’ve tried all of the steps you suggested, along with the solutions from the other threads, but I’m still facing the same issue. The only thing I’ve noticed is that the problematic container runs with a different user ID than root, whereas the other containers that work fine use root. Do you happen to know if Anysphere rely on the root user during server installation?