Chats subsequent conversations keeps on remaining stuck despite any model change or whatever you tried and it works fine when you start a new thread. This used to happen rarely, now happening very very frequently.
Steps to Reproduce
Not sure , it happens to me after 2-3 messages in any chat
I am also facing this issue since last two days. I am seeing following on Developer Tools Console.
When I reopen the cursor, it answers me 1-2 prompts but then gets hanged. I have tried all the debugging tips (including reinstallation of cursor also)
We checked your stuck turn: the request actually completed successfully on our backend. The chat client just never registered that it finished, so it kept spinning on “Planning next moves.” That’s a client-side state issue, not your network. It’s also why a new thread works, it resets the stuck state, and why it happens more as a chat grows.
Quick workarounds:
Reload the window (Cmd+Shift+P, then “Reload Window”).
Start a new chat and pull in context with @Past Chats.
If it happens again, it’d help to know whether an error eventually appears (e.g. “Agent Execution Timed Out”) or if it just spins, plus a Request ID from a stuck send.
@Pankaj_Goel Thanks Pankaj. This looks like the same client-side wedge described above: the turn finishes on our backend but the chat client keeps spinning. Because it’s a stuck-state issue rather than a bad install, reinstalling won’t help, which matches what you’re seeing.
Reloading the window (Cmd+Shift+P, then “Reload Window”) OR restarting Cursor should clear it for now. If you’d like us to take a closer look, feel free to share a request ID from the problematic turn. Ideal if you can disable privacy mode before replicating the problem.
To disable Privacy Mode:
Open Cursor Settings with Cmd+Shift+J on macOS or Ctrl+Shift+J on Windows/Linux.
Go to General.
Turn Privacy Mode off / switch to Share Data.
To get the Request ID:
Open the relevant conversation in the Chat sidebar.
I could not enable Data Sharing mode because I belong to an enterprise tenant that only allows Privacy mode.
I am experiencing this issue not only with a specific chat agent but across all chat agents. They typically work as expected for the first few prompts, but after several interactions, they begin exhibiting the same behavior and appear to become unresponsive.
One observation is that the issue seems to occur primarily within a particular workspace. I work with two separate workspaces in WSL/Ubuntu, each opened in a different Cursor window. The problem is consistently observed in one workspace, while the other appears to function normally.
Another observation is that after approximately 30–40 minutes (or slightly longer), the affected chat agent starts responding normally again. However, after a few more conversations, it becomes unresponsive once more.
For reference, the following request IDs are related to the issue:
c75bebc6-7326-4daa-8fba-3a42f1051910
1cb9e7b0-e671-43cb-9be5-f9278f0b9f7a
Could you please investigate whether this behavior could be related to the workspace, WSL environment, or some throttling/timeout/blackout windows mechanism?
