I am on Windows 11, Cursor v2. I will prompt the agent. Once it completes, I will try to scroll through the chat window to read the output or review the files, but the cursor is completely locked up, and I cannot interact with anything. I have to kill the cursor via the task manager and relaunch. Once I relaunch, the chat won’t completely render the previous run making it useless. This is happening on about 9 out of 10 prompts. Making Cursor completely unusable.
I was wondering if anyone else is experiencing this? I’ve tried completely wiping my system of Cursor and reinstalling Cursor v2 fresh, and it’s still exhibiting this behavior.
cursor 2.0.43. But this issue has happened on every v2 version. was not happening on 1.7. I have my update access set to default. I have experienced this with Sonnet 4.5. I can do some more testing to see if it happens on other models. hard to say about the prompt, I haven’t been able to use cursor much when it’s constantly locking up. But my prompts are typed out, not using the voice mode, and have been with and without / commands.
I think I have narrowed down what is happening. It appears only to happen when the agent completes, and Cursor is not in focus. For example, if I give the agent a prompt and leave it running, then go look at something in Chrome, when the agent completes, I go to click back on Cursor and Cursor is completely locked up, and I have to kill it. But if I never leave Cursor while the agent is running, it won’t freeze.
This has been an on-going issue for me too. Still haven’t found a fix but @Westy is correct, and the process will need to be killed, along with any sub processes spawned during its session. Any update on this would be greatly appreciated.