Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
When the agent modifies a file, the window will freeze when its done editing that file. The cursor helper process in the activity manager will be running at 130% cpu, and it never ends.
Steps to Reproduce
It happens everytime i ask the agent to do something. Iæ
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.7.54
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0
Additional Information
I installed version 1.6 and it doesn’t happen there
Does this stop you from using Cursor
Yes - Cursor is unusable
5 Likes
I’m experiencing the same issue. It started occurring after updating to the latest version.
3 Likes
I also experience agent mode hangs on thinking, modifying, concluding, mostly it worked under 10% of the actual tasks and need to stop it manually and tell him to resume, and redo this a couple of times to get the job done. It is very annoying and like making the daily productivity 500% slower
2 Likes
Also this issue. Window 11
Just appears window with able to restart window / close / keep waiting
i changed beta - updated acess - to early access and now its not freezing. something happened with stable version.
1 Like
Hi all, thanks for the reports.
If you are on Early Access, and need an immediate fix, please use Download · Cursor to redownload our latest stable release while we resolve this.
For anyone who can reliably trigger this issue, can you please run Developer: Toggle Developer Tools and check the Console tab for any errors that show up when the Agent tries to edit a file.
Also, please share your Cursor version and OS too - thanks!
I did the exact opposite. I’ve downgraded to v1.6 for now to move forward as the latest version was where I was facing the issue.
It appears to be related to this setting for me:
"workbench.editor.showTabs": "single"
Turning that off in the settings fixes it.
Yep experiencing this also.. I submitted a bug earlier today for it.