[Remote SSH] Opening "/" as workspace causes terminal UriError on Windows

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using Cursor Remote SSH on Windows to connect to a Linux machine, opening the remote root directory “/” as the workspace causes the integrated terminal to fail with a UriError.

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

If I open “/root” instead, the terminal works normally.

Steps to Reproduce

  1. Open Cursor on Windows
  2. Connect to a Linux machine using Remote SSH
  3. Open the remote folder “/”
  4. Click to create or open the integrated terminal
  5. Cursor shows the UriError popup

Control case:

  • If I open “/root” instead of “/”, the terminal opens normally

Expected Behavior

The integrated terminal should open normally when the remote workspace is “/”.

Screenshots / Screen Recordings

ScreenShot_2026-04-25_185534_234.png

Operating System

Windows 10/11

Version Information

IDE:
Version: 3.2.11 (user setup)
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
Build Type: Stable
OS: Windows_NT x64 10.0.26200

Remote:
Linux via Remote SSH

For AI issues: which model did you use?

N/A - not an AI model issue

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

This appears to be specific to Cursor handling “/” as the remote workspace root.

Additional notes:

  • SSH connectivity works normally
  • Opening “/root” works
  • Opening “/” reproduces the issue consistently
  • Workaround: open “/root” instead, or use an external SSH terminal and run cd /

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the clear report with steps and the control check (/root works, / fails). This is a known class of bugs with URIs on remote workspaces when the root is /. posix.join("/", ...) can produce a path with //, which then triggers a UriError. The issue is already being tracked, but I can’t share an ETA yet.

For now, the workaround is what you already found: open a specific subfolder (/root, /home/user, etc.) instead of the root /. If there’s an update on the fix, we’ll reply in the thread.