Remote Terminal URI error via ssh remote to server

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

‘[UriError]: If a URI does not contain an authority component, then the path cannot begin with two slash characters (“//”)’ error is thrown when attempting to open any terminal from the terminal menu pull down, by right clicking on a file folder or via the Command Pallette.

I have configured cursor 2.0 to use Remote ssh extension along with Remote Explorer and Remote SSH: Editing Config and my connection to all my servers is rock solid in the ide. My issue is I cannot open any terminal without throwing the above error which forces my to use my client terminal to perform all cli runs, etc which is crushing the workflow.

I have tried numerous alterations in the user/settings.json as per dialogue with AI agent . Here are the core declarations that I have been applying variations too in the User/Library/Application Support/Cursor/User/settings.json:

    "terminal.integrated.enablePersistentSessions": false,
    "terminal.integrated.shellIntegration.enabled": false,
    "terminal.integrated.cwd": "${workspaceFolder}",
    "terminal.integrated.cwdSource": "workspaceRoot",
    "terminal.integrated.defaultProfile.linux": "bash"

I have attempted to be systematic by altering the key value pairs and have documented all the alterations (which is too much for this post) but I haven’t discovered the source of the issue or found a binding that resolves the issue.

client: MBPro oxs 11, server: linux Ubuntu 24.04.1 LTS

Steps to Reproduce

Since upgrading to 2.0

Expected Behavior

Opening a terminal in the workspace should instantiate a bash terminal in the selected folder or in the root of the container.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.43 (Universal)
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin x64 20.6.0

Additional Information

I had been using Remote SSH robustly on our work server with no issues but I recently had challenges with my personal digital ocean droplet that was spiking during ssh connections. I attempted using sshfs with some success. One item that came up was my global node version (older v18.*) on my client was one possible reason for the heavy spikes and I removed the Vue Extension as that may have been using the global node (I also edited the .bash_profile to only use nvm in interactive shell only to prevent the possibility that the global node/nvm was an issue). I am ssh’ing directly into the node docker container that has a reverse proxy for the ssh and is behind an nginx proxy container on my server.

Additionally, I can open the same remote ssh connection in vscode, view the full codebase/ file structure and quickly open the terminal into any folder in that container without any issues.

Does this stop you from using Cursor

Yes - Cursor is unusable

3

After considerable research and investigation I have discovered what is causing the issue.

I am attempting to access the top level “/” or “..”, folder with the root user into the docker container via Remote SSH. This is forbidden because .cursor-servor installs in the “/root” folder and attempting to select a directory that is above that directory is what is triggering the URI errors. I want to be able to inspect the full directory structure to allow for quick updates to system services configuration files within the explorer panel. In one specific case, my nginx reverse proxy container is the front facing container on my server and I need to be able to update different .conf files as well as use the terminal for nginx -t and restarts in the terminal and manage certbot ssl certificate changes. If I select this folder (“/”) I can utilize the explorer for all the file inspections an edits but the terminal is not functional. This access barrier seems to be intentional as part of the assuring a safety mechanism but I can do this in vscode so this was very unexpected, additionally (IIRC) I thought I had been able to do this in earlier versions. If I want to use the terminal I can only establish the folder structure from “/root” as part of the ssh setup if I want to use the integrate terminal but this is not ideal from a workflow standpoint.

Does anyone else know if this has changed in the new release and does anyone else find this counterproductive?

My personal preference is to not have cursor block my ability to handle the dev ops workflow and I request this be changed to allow full file structure navigation with the integrated terminal.

I am looking at creating a Symlink but I am concerned that this is a band-aid that won’t be robust long term.

Thanks
Rafe

Thanks