Console Errors & The Connection Stalled Error in Chat/Agent - first load and chat log

[JGoo (Jim G)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When opening Cursor the developer tools console is full of error logs. Subsequent attempts to chat in Ask mode (and any mode) result in additional Connection Failed problems and Cursor is inoperable for AI chat intent.

High Level: Cursor inoperable and repeated Connection Errors.

Steps to Reproduce

1. Open Cursor,
   Open Developer Tools > Console
   Screenshot first load/run Console Errors
2. create new chat, type “tell me about the first README.md you find”
   Response “The connection stalled. Please try again.”
   Screenshot chat failure Console Errors

Note that different chat modes return different Console Errors

Expected Behavior

I do not know if errors in logs are “normal”, but the chat started failing a week ago last Thursday the expectation is normal Ask, Plan, Agent operation.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

IDE:
Version: 2.4.22
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z (2 days ago)
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: Darwin x64 23.6.0

For AI issues: which model did you use?

Auto, any

For AI issues: add Request ID with privacy disabled

Request ID: 3f272a5f-69bb-420d-b0bd-6af6e1a9ae4c
Connection stalled
LTe: Connection stalled
at rpf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4764)
at fva.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async Hyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34196:57047)
at async Zpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:7695)
at async Zpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Object.Ei [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32994:3808)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32968:59730

Additional Information

Network Settings:
HTTP/1.0 (toggled all modes and restarted between, this is lowest mode)
CloudFlare VPN disabled
WiFi Disabled - Connected to LAN

1 TB available space on disk

Note: this coincidentally started when I appeared to run out of credit for the billing period. I am now on “On Demand billing” and the IDE is still not functional.

Does this stop you from using Cursor

Yes - Cursor is unusable

[JGoo (Jim G)]

I was unable to attach more than one screenshot to the original message. Here are screenshots of the AI chat log

[JGoo (Jim G)]

Here’s something funky, the application creation date is January 1, 1980 12:00am.

[JGoo (Jim G)]

ok, so Agent Chat seems to be working now. I do not know if it is something I did or something which was done on the backend at Cursor.

However, I have lost my ability to continue any prior chat conversations however, which is better than losing 3 months of chat histories.

Procedure I took to fart around and see if I could revert to a prior version:

1. Navigate to /Applications/, create a directory called /backup/
2. COPY cursor.app into /backup/
3. Downloaded the 2.3 version here: Download · Cursor
4. Run the DMG file
5. Drag the Cursor application to Applications
6. Approve the ‘replace’ prompt
7. After completion and certificate verification open the /Applications/Cursor.app file (v 2.3.41)
8. Go to a NEW Chat, type Hello. It takes a while but then responds.
9. Go to an older Chat and it will state “Conversation Corrupted”
10. Exit the application
11. Open the /Applications/backup/Cursor.app file (v 2.4.22)
12. Go to a NEW Chat, type Hello. It will respond.
13. Exit the application
14. Drag the Cursor.app file in the /backup/ director into the /Applications/ root directory and accept the ‘replace’ prompt
15. Open the /Applications/Cursor.app file (v 2.4.22) and get back on the horse and ride.

Note, that when I first tried simply replacing 2.4.22 with 2.3.41 chat was severely latent and I saw dozens of errors in the Developer Console.

Unfortunately though… I am now hitting Git permissions problems. ho hum.

[deanrie]

Hey, looks like you partially fixed the problem, but let’s fully sort it out.

What you did (downgrade or upgrade) helped because it reset a corrupted workspace cache. That’s why old chats are now missing, that’s a side effect of the reset.

Known fix (if it comes back):
Instead of reinstalling, just rename the project folder in Finder (MyProject → MyProject_v2) and reopen it in Cursor. This resets the local index without wiping the whole app history. Details: Connection error, again and again - #3 by deanrie

About the console errors:

• OTLPExporterError is a known telemetry issue, it does not affect functionality
• Extension Host UNRESPONSIVE / Composer Extension host became UNRESPONSIVE the team is aware
• These errors look scary, but most of them are just logging noise

About the app creation date (1980-01-01):
That’s a packaging artifact, not a bug.

If Connection Stalled comes back:

1. Try the folder rename workaround
2. If that doesn’t help, go to Cursor Settings > Network > Run Diagnostics (send a screenshot)
3. Help > Toggle Developer Tools > Console. If you see red errors when sending a message, let me know

About the Git permissions issue, that’s separate. Can you describe exactly what’s not working?

[JGoo (Jim G)]

To be clear, old chats are NOT missing, they are simply not able to be continued or iterated on.

I do NOT want a scenario where I lose the old chats from the UI for visibility and historical reference purposes.

And from what I had read on resolutions to this software defect, changing the directory name will certainly make me lose my chat history. When I first started using Cursor I made a directory name change, lost my chat history and had to develop a python script to query the prior chat database to extract chats into a directory as MD files. Not sure which scenario is worse, IMO having to do work to recover is worse.

So where I sit currently, what I did hobbles me but does not cripple me. What you are proposing cripples me. If that is not the case, please me more specific on what I can expect with your proposed solution. If I lose my chat history can I rename the directory back to the prior name and get it back?

I would also contend that the application build date of MS-DOS Epoch smells like a bug. There is no scenario in my history as a software PM and Dev lead where that would have passed QA. It looks suspicious and potentially malicious not to mention can lead to a number of actual application failures including antivirus quarantine, signature rejection, auto-update failure, and backup failure to name a few. I am not an expert in contemporary mac build systems, simply harkening back to real-world experience.

I will resolve the GIT issue in another thread should it be necessary.