Describe the Bug
After replacing the official Microsoft Dev Containers plugin with the one provided by Anysphere (Cursor), the plugin no longer works as expected. I’m encountering issues that prevent it from functioning properly.
Could you please let me know if this is a known incompatibility or if there’s a workaround available?
2025-07-11 10:27:56.249 [info] Searching for devcontainer.json files
2025-07-11 10:27:56.515 [info] Found 1 devcontainer.json files: \home\alexis\maxoutil.sutunam\.devcontainer\devcontainer.json
2025-07-11 10:27:56.515 [info] Reading devcontainer config with command: read-configuration --workspace-folder \home\alexis\maxoutil.sutunam --config \home\alexis\maxoutil.sutunam\.devcontainer\devcontainer.json
2025-07-11 10:27:56.545 [info] Running devcontainer CLI command: c:\Users\WEBM3\.cursor\extensions\anysphere.remote-containers-1.0.12\dist\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js read-configuration --workspace-folder \home\alexis\maxoutil.sutunam --config \home\alexis\maxoutil.sutunam\.devcontainer\devcontainer.json --docker-path docker
2025-07-11 10:27:56.545 [info] Spawned process 26128: 'C:\Users\WEBM3\AppData\Local\Programs\cursor\Cursor.exe' 'c:\Users\WEBM3\.cursor\extensions\anysphere.remote-containers-1.0.12\dist\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js' 'read-configuration' '--workspace-folder' '\home\alexis\maxoutil.sutunam' '--config' '\home\alexis\maxoutil.sutunam\.devcontainer\devcontainer.json' '--docker-path' 'docker'
2025-07-11 10:27:56.545 [info] [read-configuration]: Running command: node
2025-07-11 10:27:56.674 [info] [read-configuration][stderr]: [2025-07-11T08:27:56.673Z] @devcontainers/cli 0.75.0. Node.js v20.19.0. win32 10.0.26100 x64.
2025-07-11 10:27:56.683 [error] [read-configuration]: Running command: node
2025-07-11 10:27:56.683 [error] Failed to read devcontainer config [read-configuration] Command failed with exit code 1: stdout:
2025-07-11 10:27:56.684 [error] Failed to reopen folder in container Failed to read devcontainer configuration
2025-07-11 10:33:32.397 [info] Checking for exec server for remote authority: wsl+debian
2025-07-11 10:33:32.397 [info] No remote exec server found for SSH authority: wsl+debian
2025-07-11 10:33:32.397 [info] No remote exec server found for authority: wsl+debian; using local
025-07-11 10:55:10.352 [info] [devcontainer up]: Running command: node
2025-07-11 10:55:10.475 [info] [devcontainer up][stderr]: [2025-07-11T08:55:10.472Z] @devcontainers/cli 0.75.0. Node.js v20.19.0. win32 10.0.26100 x64.
2025-07-11 10:55:10.475 [info] [devcontainer up][stderr]: [2025-07-11T08:55:10.472Z] Start: Run: docker buildx version
2025-07-11 10:55:10.692 [info] [devcontainer up][stderr]: [2025-07-11T08:55:10.691Z] Stop (219 ms): Run: docker buildx version
2025-07-11 10:55:10.692 [info] [devcontainer up][stderr]: [2025-07-11T08:55:10.691Z] github.com/docker/buildx v0.25.0-desktop.1 2cf9a0c0277eb26cabe7b3f77e2069437c4e33e0
2025-07-11 10:55:10.692 [info] [devcontainer up][stderr]: [2025-07-11T08:55:10.691Z]
2025-07-11 10:55:10.692 [info] [devcontainer up][stderr]: [2025-07-11T08:55:10.691Z] Start: Run: docker -v
2025-07-11 10:55:10.751 [info] [devcontainer up][stderr]: [2025-07-11T08:55:10.750Z] Stop (59 ms): Run: docker -v
2025-07-11 10:55:10.752 [info] [devcontainer up][stderr]: [2025-07-11T08:55:10.750Z] Start: Resolving Remote
2025-07-11 10:55:10.754 [info] [devcontainer up][stderr]: Error: Dev container config (c:\home\alexis\***.***\.devcontainer\devcontainer.json) not found.
2025-07-11 10:55:10.754 [info] [devcontainer up][stderr]: at H6 (c:\Users\WEBM3\.cursor\extensions\anysphere.remote-containers-1.0.12\dist\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:2:1599509)
2025-07-11 10:55:10.754 [info] [devcontainer up][stderr]: at async BC (c:\Users\WEBM3\.cursor\extensions\anysphere.remote-containers-1.0.12\dist\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:2:1601238)
2025-07-11 10:55:10.754 [info] [devcontainer up][stderr]: at async d7 (c:\Users\WEBM3\.cursor\extensions\anysphere.remote-containers-1.0.12\dist\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:2:1674755)
2025-07-11 10:55:10.754 [info] [devcontainer up][stderr]: at async f7 (c:\Users\WEBM3\.cursor\extensions\anysphere.remote-containers-1.0.12\dist\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:2:1674413)
2025-07-11 10:55:10.754 [info] [devcontainer up][stderr]: at async c:\Users\WEBM3\.cursor\extensions\anysphere.remote-containers-1.0.12\dist\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:2:1597484
2025-07-11 10:55:10.762 [error] [devcontainer up]: Running command: node
2025-07-11 10:55:10.763 [error] Error resolving dev container authority [devcontainer up] Command failed with exit code 1: stdout: {"outcome":"error","message":"Dev container config (c:\\home\\alexis\\***.***\\.devcontainer\\devcontainer.json) not found.","description":"Dev container config (c:\\home\\alexis\\***.***\\.devcontainer\\devcontainer.json) not found."}
Thanks in advance for your help.
Steps to Reproduce
After replacing the official Microsoft Dev Containers plugin with the one provided by Anysphere (Cursor), the plugin no longer works as expected. I’m encountering issues that prevent it from functioning properly.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
Does this stop you from using Cursor
Yes - Cursor is unusable