Cursor 1.6.26 breaks Dev Container Extension

[Grevil]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Before the update to 1.6.26 I could simply run cursor --folder-uri "vscode-remote://attached-container[...] to attach cursor to a running container.

Now this command opens the cursor cli agent, with the prompt --folder-uri-vscode-remote://attached-container[...], without opening an attached instance of cursor!

This completely breaks our workflow. If I try to run cursor editor --folder-uri "vscode-remote://attached-container[...] instead, an error appears:
“error: unknown option ‘–folder-uri’”

Steps to Reproduce

Try running run cursor --folder-uri "vscode-remote://attached-container[...] to attach cursor to a running container.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.26 (user setup)
VSCode Version: 1.99.3
Commit: 6af2d906e8ca91654dd7c4224a73ef17900ad730
Date: 2025-09-16T17:12:31.697Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. We’re aware of this issue. I believe it’ll be fixed soon.

[Olynn (Fernando)]

I’m having the same issue. It broke our workflow to connect to vm instances aswell.

[ravirahman]

Hi, could you try upgrading to Cursor 1.6.27? This issue should be fixed in this version.

[Grevil]

Yes, upgrading to 1.6.27 fixed the issue for me! Thanks!

Appreciate the fast replies!