Very often my request gets stuck at ‘generating…’. This has been happening since March (when I first started using Cursor).
Half of the time a pop-up appears that suggests I there may be an issue with my connection or VPN and offers to ‘Resume’. Without changing anything about my connection I click ‘Resume’ and this fixes the issue. So evidently the problem was recoverable, but for some reason Cursor needed me to click a button before it would work.
Half the time, however, this pop-up doesn’t appear. So I restart Cursor and send the same request → it works. This happens very often.
My intuition tells me that this has to do with how much time has passed since my last request. If I took time reviewing the code and more than 10 minutes has passed - the chat ‘goes cold’ and is very likely to fail. If I’m doing minor adjustments and submitting requests one per minute - I think it always works fine.
Initially I almost stopped using Cursor. Luckily I quickly discovered that restarting it reliably fixes the problem. But its annoying af.
I mostly use gemini-2.5-pro.
I think it happens with claude-4-sonnet too, but I don’t use it as often, I’m not 100% sure.
There is a separate pop-up which says that there is a problem with a particular model provider. It appears much less often. I only got it a couple of times.
Hey, for anyone facing this, it’d be great if the next time you see this, you can run the Developer: Toggle Developer Tools command, and send a screenshot of the Console tab!
This will likely have some errors there that will point to the issue and, hopefully, how to fix it for us!
directly after 25 calls have been hit (so the chat had no time to go “cold”), i.e.,
→ 25 calls has been put through
→ option “resume” is offered
→ cursor shows VPN connection problems on ever push of “resume”
workbench.desktop.main.js:2094 [composer] submitChatMaybeAbortCurrent errored! TypeError: Cannot convert undefined or null to object
at Function.assign ()
at GW.submitChatMaybeAbortCurrent (workbench.desktop.main.js:2094:14713)
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:2094
await in submitChatMaybeAbortCurrent
resumeChat @ workbench.desktop.main.js:2094
L.rerun @ workbench.desktop.main.js:2094
(anonymous) @ workbench.desktop.main.js:2276
got another one. this one could be more heplful, atleast it tells me more. seems like an image got lost on the way, which is interesting because in the initial prompt was no image (in the overall conversation was an image once, though).
So, I’ve encountered this problem with claude-4-sonnet. This is what was in the developer’s console.
workbench.desktop.main.js:4021 Error fetching branches: Error: Could not determine default branch
Ie @ workbench.desktop.main.js:4021
4Uncaught ResizeObserver loop completed with undelivered notifications.
3workbench.desktop.main.js:4021 [Background Composer] No preferred remote found after 10 attempts
_e @ workbench.desktop.main.js:4021
Uncaught ResizeObserver loop completed with undelivered notifications.
3workbench.desktop.main.js:4021 Error fetching branches: Error: Could not determine default branch
Ie @ workbench.desktop.main.js:4021
2Uncaught ResizeObserver loop completed with undelivered notifications.
3workbench.desktop.main.js:4021 [Background Composer] No preferred remote found after 10 attempts
I don’t know how long it’s been there, so I stopped the request, cleared the console and submitted it again. After some time (10-20 seconds) I got the attached log:
Restarting the app fixed the issue and the same request to the same model worked immediately fine.
But overall I’m not encountering this problem as often as I used to. It may have something to do with me switching to claude for most of the work.
Or the new cursor version.
Version: 1.1.2
VSCode Version: 1.96.2
Commit: 87ea1604be1f602f173c5fb67582e647fcef6c40
Date: 2025-06-13T00:28:07.271Z
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-141-generic
If this only happens when clicking Resume after 25 tool calls, can you confirm if this is resolved with the new pricing plan, as this removes the 25 tool call limit?
