Connection Failed - Cursor Stops accepting Commands

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

A critical and frequent bug exists in the Cursor chat interface where, upon attempting to send a message, an error occurs. The most frustrating part is that this error completely deletes the entire unsent message from the input field. This results in a significant loss of time and productivity, especially after composing long or complex prompts. This issue is not a one-off event but happens consistently, making the chat feature unreliable and frustrating to use.

Request ID: e3f77342-8840-4aea-9da6-3f31bc49f5b5
ConnectError: [unknown] Connection failed.
at dse.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2101:9419)
at async Object.bi [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4064:28260)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4064:14403

Steps to Reproduce

Open Cursor and navigate to the chat interface (either with the AI assistant or a codebase-aware chat).

Compose a message. For higher reproducibility, make it a longer message (e.g., 3+ sentences or a complex code-related prompt).

Click the “Send” button (or press Enter).

Observed Result: Instead of sending, an error notification (often transient or non-descriptive) briefly appears. The chat interface may freeze for a second.

The user’s input field is then cleared, and the meticulously written message is permanently gone with no way to recover it.

Expected Behavior

The message should send successfully.

If a network or server error occurs, the message should not be deleted from the input field. The UI should display a clear, persistent error message (e.g., “Failed to send. Click to retry.”) and preserve the text so the user can attempt to send it again or copy it for safekeeping.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.4.5 (Universal)
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

During the middle of long task OR in between tasks, with almost all Agents, when I issue a command it does not accept the commad/prompt and just drops back , no thinking, no error. When I delete all the text in the prompt box , I get “connection failed”

Request ID: 9d6fdb7b-0971-41e1-9f37-54854e4b133f
ConnectError: [unknown] Connection failed.
at ure.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/erik/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4350:9355)
at async Object.wr [as onSubmit] (vscode-file://vscode-app/c:/Users/erik/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4642:88696)
at async vscode-file://vscode-app/c:/Users/erik/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4642:70297

Happens ALL the time now and I have no idea how to fix this. Usually 3-5 commands into a new chat and this happens. GPT5-Mini is the only one that’s gone 10+ commands..

This messes up my flow and I ahve to repeat the instructions with a new chat wasting tokens. it’s a nightmare…

Steps to Reproduce

Yes, just 2-4 prompts into a new chat..

Expected Behavior

An agent is supposed to action the prompt.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.5 (user setup)
VSCode Version: 1.99.3
Commit: 823f58d4f60b795a6aefb9955933f3a2f0331d70
Date: 2025-08-25T17:40:25.290Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like
3

Request ID: d9ba6a3e-64dc-4906-839c-f37624445980
ConnectError: [unknown] Connection failed.
at ure.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/erik/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4350:9355)
at async wr (vscode-file://vscode-app/c:/Users/erik/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4642:88696)

4

Hi @Erik_Z , sorry to hear you’ve been having some issues with Cursor!

Unfortunately, neither of those request IDs could be found on our internal system, which suggests one of two things:

Firstly, it may be that your device or networking setup is not allowing Cursor to correctly “phone home” to its servers, which is not only stopping your chat messages from working, but also stopping the request IDs from properly registering with our system.

To confirm this, can you open the Cursor Settings page (Command Palette -> Cursor Settings), switch to the Network tab, and run the Diagnostics. If all comes back green, everything should be fine, but if you see any errors, it likely means your network or device is blocking the connectivity to Cursor’s servers.

Alternatively, it may be that a client-side issue is causing Cursor to not function correctly. If you have attempted the network diagnostics and seen no errors or problems, can you open the Developer Tools (Command Palette -> Developer: Toggle Developer Tools), switch to the Console tab, and check for any errors?

Some errors can be expected, but anything that happens repeatedly when you attempt to submit a chat message is likely the cause - if you get one of these, do send it back to us here!

5

Yes I actually checked , here’s a dump from when the error occurs.

Uncaught ResizeObserver loop completed with undelivered notifications.

workbench.desktop.main.js:4350 [composer] Failed to update checkpoint with attached code chunk files: Error: [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash (“/”) character at yWc (workbench.desktop.main.js:50:67955) at new vRn (workbench.desktop.main.js:50:72165) at new bFe (workbench.desktop.main.js:50:73627) at bFe.with (workbench.desktop.main.js:50:72601) at pLd.resolveRelativePath (workbench.desktop.main.js:7003:42777) at ure.submitChatMaybeAbortCurrent (workbench.desktop.main.js:4350:943) at async Object.wr [as onSubmit] (workbench.desktop.main.js:4642:88696) at async workbench.desktop.main.js:4642:70297

workbench.desktop.main.js:4350 [composer] submitChatMaybeAbortCurrent errored! Error: [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash (“/”) character at yWc (workbench.desktop.main.js:50:67955) at new vRn (workbench.desktop.main.js:50:72165) at new bFe (workbench.desktop.main.js:50:73627) at bFe.with (workbench.desktop.main.js:50:72601) at pLd.resolveRelativePath (workbench.desktop.main.js:7003:42777) at workbench.desktop.main.js:4350:2036 at Array.map () at workbench.desktop.main.js:4350:1998 at Array.flatMap () at ure.submitChatMaybeAbortCurrent (workbench.desktop.main.js:4350:1944) at async Object.wr [as onSubmit] (workbench.desktop.main.js:4642:88696) at async workbench.desktop.main.js:4642:70297

workbench.desktop.main.js:4350 [composer] Failed to get complete AI response

6

GPT mentioned it could be related to file attachments, but I am not attaching files in my prompts. , I will leave it to you for analysis.

8

ı have same issue cursor 1.5 version.

Request ID: 38664f78-f66f-4806-aecb-34a5ef9b94c7
ConnectError: [unknown] Connection failed.
at ure.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Nurullah/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4350:9355)
at async wr (vscode-file://vscode-app/c:/Users/Nurullah/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4642:88696)

The problem occurs after using the AI chat feature for some time. Once this error appears, I cannot use the AI chat functionality in that tab anymore. The error seems to be related to connection failure, but my internet connection is stable and working properly.

9

Thanks for reporting this.

Your version (1.4.5) is older than the current version (1.5.7). Please update to the latest version first and retest.

I was not able to reproduce this on the latest version. The input text stays and just the error message comes up.

Screenshot 2025-08-29 at 3.09.07 PM
Screenshot 2025-08-29 at 3.09.07 PM588×216 15.3 KB

If the Network issue persists after updating:
• Run network diagnostics: Go to Cursor Settings → Network → Run Diagnostics to check your connection
• If on a corporate network or VPN, try disabling HTTP/2: Press Cmd+, → search “HTTP/2” → enable “Disable HTTP/2”

Please let us know if this still happens after these steps

10

Request ID: 1313b336-35eb-4e52-85f9-1ea32c120234
ConnectError: [unknown] Connection failed.
at ure.submitChatMaybeAbortCurrent (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4292:9355)
at async Object.wr [as onSubmit] (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4584:88696)
at async vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4584:70297

Same story

No model will work - all just insta-returns, no error other than this

11

And diagnostics run - all green

1 Like
12

Thank you all for your bug reports. Team is checking and may request additional info as we have to reproduce it internally as well.

13

Request ID: f22bb153-447a-4e15-bed3-9f573c06d7e5
ConnectError: [unknown] Connection failed.
at ure.submitChatMaybeAbortCurrent (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4292:9355)
at async Object.wr [as onSubmit] (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4584:88696)
at async vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4584:70297

Sigh.

14

If I go back to the prior request - and then edit that, in this case I was able to “unskunk” the session and have it continue, no connection error (for now) let’s see what happens once it gets to the end of this run.

15

Nnnnnope. Actually skunked like the bad old Nov ‘24 days of “context is full, FU dude”.

context reports that it is only 52.3% full, but after the run continued, attempts to make another request in that chat resulted in:
Request ID: 09c54803-c7cd-4035-9776-4ddb9f4e90fc
ConnectError: [unknown] Connection failed.
at ure.submitChatMaybeAbortCurrent (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4292:9355)
at async dHs.submitQueueItem (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:5524:12554)
at async dHs.submitNudges (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:5524:13447)
at async dHs. (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:5524:10791)
at async ewe. (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:1544:7329)
at async wZ.processCodeBlocks (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:1500:3713)
at async ure.submitChatMaybeAbortCurrent (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4292:5969)
at async Object.wr [as onSubmit] (vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4584:88696)
at async vscode-file://vscode-app/h:/Apps/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4584:70012

if you read the logs/chat, apologies for the salty language.

—-

Just to be extra clear:

  1. attempts to ADD new entry to the chat, fails with connection error as shown
  2. returning to LAST SUCCESSFUL, pre-error chat entry, and then editing and resubmitting that - will actually succeed and proceed with doing work.
  3. after work done, returns to state #1 - i.e. the chat is skunked and I know of no way to allow it to continue. abandon all context and start over.

–

OK, further investigation, if I “duplicate chat” from the point of “not yet skunked” I can create a copy of the chat context that will continue / is not skunked. A workaround for anyone that comes across this :folded_hands:

16

I was able to recover a dead chat, the next day after no using it for 24 hours. Machine restart etc… I have no idea why it worked, I got about 2 hours out of it before it did it again.

OK I ran the dev console through Claude on Cursor and it narrowed it down to this.
”You’re absolutely right! The URI error is indeed the critical issue that’s preventing the chat/composer from working. Let’s focus on that specific error:

[composer] submitChatMaybeAbortCurrent errored! Error: [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash ("/") character

This error is happening when Cursor’s composer tries to resolve file paths, and it’s encountering malformed URIs. Let’s investigate and fix this:

[1 tool called]

I notice you’re working in xxxx on a Linux system, but the error shows Windows paths xxxx . This path mismatch between Windows and Linux is likely causing the URI error.

The issue is that Cursor is running on Windows but trying to work with files on a Linux system (possibly through WSL or remote SSH), and the path resolution is failing.

Let’s check how you’re connecting to this Linux system:

[2 tools called]

Perfect! Now I understand the issue. You’re using Cursor on Windows to connect to a remote Linux server via SSH. The URI error is happening because Cursor’s composer is trying to resolve file paths using Windows-style paths when it should be using Linux-style paths for the remote connection.

The Root Cause:

The error [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash ("/") character occurs when Cursor tries to construct file URIs incorrectly. It’s mixing:

  • Windows paths from your local Cursor installation
  • Linux paths from your remote server

Solutions:

Solution 1: Check Your Cursor Remote Connection Settings

[1 tool called]

Solution 2: Create Cursor Settings to Fix Path Resolution

Let’s create a workspace settings file to help Cursor properly resolve paths:

[2 tools called]

Solution 3: Fix the Workspace File

[1 tool called]

The workspace file looks correct. Now let’s create a fix for the composer/chat issue:

Solution 4: Create a Cursor-Specific Configuration

[1 tool called]

Immediate Actions to Fix the Composer/Chat:

1. Restart Cursor Completely

  • Close Cursor completely (File → Exit or Alt+F4)
  • Reopen Cursor
  • Reconnect to your SSH remote

2. Clear Cursor’s Cache (Run on your Windows machine, not the Linux server)

# In Windows PowerShell:
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Programs\cursor\Cache"
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Programs\cursor\CachedData"

3. Check Your SSH Connection Method

When reconnecting, ensure you’re using:

  • Remote-SSH extension properly
  • Connect via: Ctrl+Shift+P → “Remote-SSH: Connect to Host”
  • Select your server: xxx

4. Alternative: Use Cursor’s Built-in Terminal

If the composer still fails, try:

  • Open Cursor’s integrated terminal (Ctrl+`` or View → Terminal)
  • Check if the terminal shows the correct Linux path
  • If not, the remote connection isn’t properly established

5. Verify Remote Extension Host

After reconnecting:

  • Check the bottom-left corner of Cursor - it should show “SSH: xxx
  • If it doesn’t show this, you’re not properly connected via SSH

The Core Issue:

The composer is failing because it’s trying to use Windows file URI syntax xxx when working with Linux paths xxx . This happens when:

  1. The remote SSH connection isn’t properly established
  2. Cursor is trying to use local Windows paths instead of remote Linux paths
  3. The workspace isn’t properly configured for remote development

After applying these fixes and restarting Cursor with a proper SSH connection, the composer/chat should work correctly. The key is ensuring Cursor knows it’s working with a remote Linux system, not local Windows files.”

I am yet to action all of this, so I will reply soon.

1 Like
17

Ok my suggestion, copy the Dev console of Cursor and Feed it into Opus 4 or Gpt5-High and get them to ■■■■■ the errors - it;s the URI error.. to save on the size of the console output, close and restart Cursor.. , find your broken chat session get the error. Open Dev Tools under HELP then go to Console > Save As.. load this into your agent for analysis.

For me, we deleted some stuff and relaunched… (save your workspace locally) , The AI agent gave me a new config file (forgot which one) and now I’ve been cranking out code with GPT5 for a few hours, no issues.

18

Anecdotally, I buy it. I just referenced a file outside of the current repo, and it errored out in the traditional manner. Fixing one tool with another tool, I’ll give it a go!

1 Like
19

Gav, cursor app is just trash right now. My only consistent stable fallback is to use the Cursor-CLI Cursor-agent is saves session history and you can reload, just be sure to exit normally and you’ll get the session restart prompt. I’ve been using GPT5 as the claude agents tend to fake content often.

Let’s hope they find a solution soon for the main app.

20

A regression was introduced in Cursor v1.4 that causes this bug. It didn’t exist in v1.3. This issue is particularly frustrating for me, as I heavily rely on the remote tunnel feature for my daily workflow, which involves developing on Windows while connected to a remote Linux machine.
@Erik_Z @condor @sanjeed5 @danperks

21

hi @1821746019 I am not sure about 1.4 but we are now at 1.6 and this is the only version that currently receives support. Can you update and check if the issue still exists on latest 1.6 version?

Is you are using Remote SSH it would be best time to file a bug report for it now as we are looking into Remote SSH issues. Create Bug Report