Agent connection error - remote SSH - when console open

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

On windows when connected to a remote windows system via SSH I am able to browse files, edit files, etc. but the agent shows a connection error. It seems to be specifically when the console is showing. If I hide the console, I am able to use the agent again, but when I show the console, the agent connection error comes back. In the developer tools, this error shows.

[composer] submitChatMaybeAbortCurrent outer error Error: [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash (“/”) character
at ANd (workbench.desktop.main.js:50:67655)
at new ZBs (workbench.desktop.main.js:50:71872)
at new TWe (workbench.desktop.main.js:50:73340)
at TWe.with (workbench.desktop.main.js:50:72308)
at rpm.resolveRelativePath (workbench.desktop.main.js:14986:42831)
at workbench.desktop.main.js:10004:1172
at Array.map ()
at KK.getPopulatedContext (workbench.desktop.main.js:10004:1135)
at KK.submitChatMaybeAbortCurrent (workbench.desktop.main.js:9988:7914)
at async bo (workbench.desktop.main.js:12254:3831)

Steps to Reproduce

Open cursor
Open a project via SSH on a remote windows computer
Toggle on the console
Try sending a message to the agent

Expected Behavior

Agent should respond to requests

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44 (user setup)
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto

Additional Information

This seems to have been a bug that existed in prior versions and was fixed, but it seems to be back now.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report.

This is a known regression - the UriError in resolveRelativePath is a Windows path parsing bug when collecting terminal context.

Workaround: Switch the bottom panel from Terminal to Output (select “Remote-SSH” in the dropdown). This should allow agent to work while terminal context isn’t collected.

Similar reports:

The team is tracking this. Let me know if the workaround helps.

Thank you, yes the workaround works but is definitely not ideal when developing command-line tools. Is there an ETA by chance on this regression getting fixed/released?

Unfortunately we don’t have an exact ETA yet. This is a regression that came back in recent versions after a previous fix.

For now, the workaround using the Output panel is still the main solution. I get that this is inconvenient when you’re developing CLI tools.

I just updated and it seems this regression has been fixed. I’ll post back if I notice it break again.

Nevermind, I lied, it’s still broken.

Same problem

I completely uninstalled it and then reinstalled version 2.2.44, which resolved the issue.
The SSH plugin version is 1.0.38.

1 Like