Describe the Bug
I have the following extensions installed in Cursor:
-
anysphere.remote-containers
-
ms-vscode.remote-server
I’m starting a devcontainer using the Devcontainer CLI, and I’m trying to open Cursor attached to this running devcontainer using the following script:
CONF=$(printf '{"settingType":"container", "containerId":"%s"}' "$devcontainer_id")
hex_config=$(printf "$CONF" | od -A n -t x1 | tr -d '[\n\t ]')
cursor --folder-uri "vscode-remote://attached-container+${hex_config}${folder}"
Cursor launches, but it doesn’t open the devcontainer. In the Extension Host Output, I see this error:
2025-07-07 20:23:46.988 [info] [resolveAuthority(attached-container,1)][0ms] activating resolver for attached-container+7b2273657474696e67547...
2025-07-07 20:23:46.988 [error] [resolveAuthority(attached-container,1)][0ms] no resolver for attached-container undefined
Any idea how to make this work with Cursor?
Works fine for vscode tho.
Steps to Reproduce
- Start any devcontainer useing devcontainer CLI
- Open cursor with setting provided above using containerId
Expected Behavior
While the attached-container authority works as expected in VS Code, it throws an error and fails to resolve in Cursor.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.1
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:06:37.704Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
Does this stop you from using Cursor
No - Cursor works, but with this issue