After I remove past chat from the context, it worked out but losing context, too. 
I am very upset about this error. I can’t imagine that the solution to this problem is to clear the chat history.
1 Like
Found the fix. I was on Linux Mint - and I read a lot of comments from other Cursor peeps but my fix was, log into Cursor, go to settings then look for active sessions (it was Cursor - The AI Code Editor at my time of testing), remove cursor App from desktop, start a NEW chat in cursor… it will log you back in, then you can go back to your old chat… Happy vibe coding Cursorlites … found a really cool Ai prompting technique today I asked cursor to integrate my python and curl apps into Streamlit - and it literally made me a GUI app so I do not need to run any commands, enter proxies, upload spreadsheets blew my mind!!! It is taking Vibe Coding to a new level
No worry with ur contribtion buddy 
thank you so much
Tried removing sessions, restarting - it works (Cursor relogins) but for maximum 1 hour.
2 workspaces - one with Linux kernel, one with QEMU, paid for “pro”, Cursor 1.1.6, why is it doing it?
And when it fails, what to test in the network? Ping, wget, what exacly? Thanks,
Still an issue. After a few minutes, shows another error:
Request ID: 4734d1da-0ac6-4551-9b1b-a03634f6f1ed
ConnectError: [unknown] No response from model
at cie.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2072:22878)
at async At (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4019:18803)
I started getting this issue only recently. The past week or two has been horrible, the error pops up several times a day. But before, it worked just fine without any issues with and without VPN. So I suspect it’s a recent change that’s causing this issue.
1 Like
I also started having this issue at exponentially higher rates this past week. It turned out to be the latest version 1.2.4 which is the root cause. Switched back to 1.2.1 (latest appimage available for linux officially is this one) and it looks good until now
Thanks so much bro