[URGENT] Agent stops working after the first message

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agent chat stop working after the first message and prompt me this:

Request ID: fa420280-047a-442f-a820-1354e57140c5
mje: [internal] [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash (“/”) character
at mdf (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9094:26624)
at ddf (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9094:25527)
at xdf (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:4393)
at kfa.run (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9095:7579)
at async Byt.runAgentLoop (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34199:57735)
at async apc.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34248:7695)
at async apc.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34248:8436)
at async DTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9168:74456)

Steps to Reproduce

connect to codebase with ssh, send a message in the agent chat, wait til it finishes the first response, send another message, it don’t work

Operating System

Windows 10/11

Version Information

Version: 2.4.7 (system setup)
VSCode Version: 1.105.1
Commit: ca0f9bf806f235ea014a22712cbcbf5e88ca77e0
Date: 2026-01-20T20:52:38.077Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

auto model

For AI issues: add Request ID with privacy disabled

Request ID: fa420280-047a-442f-a820-1354e57140c5

Additional Information

I had the same problem with the latest version as well, i downgraded just to make sure

Does this stop you from using Cursor

Yes - Cursor is unusable

Write and StrReplace tools return "Invalid arguments" when workspace is opened via Remote-SSH (Mac → Windows)
A path resolution error occurs when using an SSH remote environment
4

Hey, thanks for the report. This is a known regression. It’s an error when parsing Windows paths while collecting terminal context in Remote SSH.

Temporary workaround:
Switch the bottom panel from Terminal to Output. This should let the agent work while terminal context isn’t being collected.

To help us dig in, can you share:

  • The Anysphere Remote SSH extension version (Ctrl + Shift + X, find Remote-SSH, check the publisher. It should be Anysphere, not Microsoft)
  • The OS on the remote server (Linux or Windows?)
  • Logs: View > Output > select “Remote-SSH” in the dropdown

Same issue: When working on a remote SSH server, the first session runs normally, but subsequent sessions prompt the error An unexpected error occurred on our servers
A user there confirmed that downgrading to version 2.2.44 fixed it, but that’s not a long-term solution.

Let me know if the Output panel workaround helps.

5

Hello, the bottom panel was focused on ports since i was port forwarding.

To help you investigate the problem, here’s your answers:

  • yes the ssh remote is anysphere not microsoft:
    Name: Remote - SSH
    Id: anysphere.remote-ssh
    Description: Open any folder on a remote machine using SSH and take advantage of Cursor’s full feature set.
    Version: 1.0.38
    Publisher: Anysphere

  • The OS remote is windows

  • the ssh logs but i don’t think they really related to the problem: 2026-01-27 15:55:13.942 [error] [tunnel-forwarding][::1:8080 → 127.0.0.1:5720 → localhost:8080][e6a299ec-ee75-45fe-9b61-5401dbf703bb] local connection threw an error A system error occurred (read ECONNRESET)

    2026-01-27 15:55:13.942 [info] [tunnel-forwarding][::1:8080 → 127.0.0.1:5720 → localhost:8080][e6a299ec-ee75-45fe-9b61-5401dbf703bb] local connection closed

    2026-01-27 15:55:14.696 [error] [tunnel-forwarding][::1:3000 → 127.0.0.1:5720 → localhost:3000][c10a6e98-e00d-4114-8d43-abebe1af5b2c] local connection threw an error A system error occurred (read ECONNRESET)

    2026-01-27 15:55:14.696 [info] [tunnel-forwarding][::1:3000 → 127.0.0.1:5720 → localhost:3000][c10a6e98-e00d-4114-8d43-abebe1af5b2c] local connection closed

    2026-01-27 15:55:16.551 [error] [tunnel-forwarding][::1:3000 → 127.0.0.1:5720 → localhost:3000][728dd1e6-50e3-4fdd-8924-fa4e3b9e7b5c] local connection threw an error A system error occurred (read ECONNRESET)

    2026-01-27 15:55:16.551 [info] [tunnel-forwarding][::1:3000 → 127.0.0.1:5720 → localhost:3000][728dd1e6-50e3-4fdd-8924-fa4e3b9e7b5c] local connection closed

I tried to switch the chat from ports to output and resent the message but it still don’t work

I will downgrade then to the 2.2.44 version for the current moment.

Hope this problem is fixed soon.

1 Like
7

maybe we have the same problem ,I’ve tried switching the bottom panel from Terminal to Output, but it didn’t work. My remote tool isn’t Microsoft’s official one, and the remote host is running Windows.finally i installed the 2.2.41 worked 2.3.41 has the same issue

9

I’ve tried switching the bottom panel from Terminal to Output, but it didn’t work. My remote tool isn’t Microsoft’s official one, and the remote host is running Windows.

11

Yes switching to version 2.2.44 solved the problem for me as well, tested it today no problem so far!