Stuck "generating... " after upgrade to annual subscription

Describe the Bug

I’ve upgraded to annual subscription and team membership, and invited a team member to the project, but after doing so the cursor keeps getting stuck at “generating” in the middle of every task.

The cursor in up to date. I started new chats, restarted the whole window, restarted the ide, restarted the computer - and done everything I possibly can.

The problem is there no matter what model I use, regardless of what project or question I ask.

Steps to Reproduce

Just ask a question with any model, any task, any project, etc.

Expected Behavior

Stuck “generating” in the middle of the task.

Screenshots / Screen Recordings

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.4
VSCode Version: 1.96.2
Commit: e86fcc937643bc6385aebd982c1c66012c98cae0
Date: 2025-06-19T02:14:02.612Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 5.15.0-142-generic

Does this stop you from using Cursor

Yes - Cursor is unusable

Request ID: 94b93cc1-5950-44b5-b859-c31d157e71e2
ConnectError: [aborted] read ECONNRESET
at dTa.$endAiConnectTransportReportError (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4246:218739)
at Xjs.S (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:494:17406)
at Xjs.Q (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:494:17184)
at Xjs.M (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:494:16272)
at Xjs.L (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:494:15373)
at Spt.value (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:494:14165)
at ye.B (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46:2398)
at ye.fire (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46:2617)
at NQe.fire (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4228:10378)
at u.onmessage (vscode-file://vscode-app/tmp/.mount_CursorFLnBCU/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6710:12344)

Hello! Dev for Cursor here. Can you try this download out and let me know if it solves the problem for you?

Download Links:

macOS:
Apple Silicon DMG

Windows:
Windows x64 Setup
Windows ARM64 Setup

Linux:
Linux x64 AppImage
Linux ARM64 AppImage

I just updated to 1.1.6
I’ll try that one first, if I still have the issue I’ll try the one you linked to. I suppose I’ll have to completely uninstall Cursor first?

I have not tested the version you posted here yet, but I still have the issue in 1.1.6
I also think I found what’s going on when it comes to the agent thinking the changes haven’t applied correctly.

When code is replaced, there is an increased chance the linter will return that there are issues. This is because the changes have not yet been applied (waiting for me to approve them)

When it’s just code being removed or added, then it’s less likely the linter will return errors and then the agent does continue with the next step.

Since there are not many reports of this, I’m thinking it might be some setting or extension on my end causing unintended behaviour?
Actually I see there is a toggle for auto fix lint errors, I’ll try switcjing it off and get back to you.

1.1.6 still showed the same issues.
I ran the test build in a Sanboxie-Plus container and asked it do some automated tasks and as far I can see the test build work as intended.
Here’s the chatlog of the testbuild

cursor_build_a_duplicate_file_scanner_i.md.txt (46.2 KB)

I don’t know what happened, still in 1.1.6 and now everything seems to work fine