UriError occurs when selecting the root path via Open Folder after attaching to a Kubernetes container

[inkoon (Lee Inkwon)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After entering a Kubernetes container using Attach Cursor, I open Open Folder and select the root directory (/). At that point, Cursor throws the following error:

[UriError]: If a URI does not contain an authority component, then the path cannot begin with two slash characters (“//”)

This seems to be caused by incorrect URI handling for the root path in the attached container environment. Instead of opening the root directory normally, Cursor fails with the URI parsing error.

Steps to Reproduce

1. Attach Cursor to a Kubernetes container.
2. Inside the attached container session, click Open Folder.
3. Select the root directory (/).
4. Observe that Cursor fails and shows the following error:
   [UriError]: If a URI does not contain an authority component, then the path cannot begin with two slash characters (“//”)

Operating System

MacOS

Version Information

Version: 2.6.18
VSCode Version: 1.105.1
Commit: 68fbec5aed9da587d1c6a64172792f505bafa250
Date: 2026-03-10T02:01:17.430Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the detailed report. This is a known issue. When you select the root directory / as the workspace folder in a remote environment (SSH, containers, Kubernetes), the URI constructor creates a path that starts with //, which fails validation.

A similar report was discussed here: Remote Terminal URI error via ssh remote to server

Workaround: Select a subdirectory instead of /, like /root, /home, or whatever folder you actually need. This avoids the URI parsing issue.

The team is aware of this. There’s no ETA yet, but your report helps us prioritize it. Let us know if the workaround works for your use case.