Same case here, macOS Tahoe 26.3.1. Rolling back to 2.6.22 worked to me.
Same crash here since the release of Cursor 3.
Hey @Ariel_Coyant, @ruan_hc, @Betsy, @TonyW, @lazer, @cbusiness, @Maksim_Kochkin, @paintoshi, @tune1472, version 3.1 is out. Please try updating and check if the issue still happens. Post the result here.
Same issue after 3.1 update.
Same issue for me even after upgrading to 3.1.10
Version: 3.1.10
VSCode Version: 1.105.1
Commit: dacbe9b31599a253763e4910eb6ab38704653320
Date: 2026-04-13T11:39:16.806Z (1 day ago)
Hey everyone, I need a hand with testing. I still canāt reproduce this on Tahoe 26.4 with the latest Cursor.
@Maksim_Kochkin you said youāre on macOS 26.4. Can you try the latest Cursor version (3.1.10 or newer) and let me know if it still freezes?
@tune1472 @amatt what Tahoe version are you on? If itās not 26.4, please try updating macOS. Apple shipped a bunch of bug fixes in 26.3.2 and 26.4: What's new in the updates for macOS Tahoe 26 - Apple Support
Iām trying to figure out if this is a Cursor bug or something macOS needs to fix. If anyone on Tahoe 26.4 + Cursor 3.1.x still sees freezes, please share the log from ~/Library/Application Support/Cursor/logs/main.log.
main.txt (14.3 KB)
Iām on 26.4 and still seeing freezes with Agent Window only since Cursor 3 release including just now. I attached my main.log but renamed main.txt since this site doesnāt allow .log uploads.
Iāve updated to 3.1.14, so far itās working, and the agent chat that previously caused a freeze can now be opened. Iāll let you know if it happens again.
@deanrie I was on a Tahoe version below 26.4, so cursor 3.1.10 crashed and stoppped working. but then I downgraded cursor to 2.6 and everything was normal again. Then After that I updated my Tahoe version to the latest (26.4) and then updated cursor to :
Version: 3.1.14
VSCode Version: 1.105.1
Commit: d8673fb56ba50fda33ad78382000b519bb8acb70
Date: 2026-04-14T01:39:23.679Z (1 day ago)
So now all is working again. I am not experiencing any issues now
Thanks for the log, itās really helpful. I can see repeated CodeWindow: detected unresponsive, the window freezes while computing a diff during agent state prefetch. This looks like the same pattern we had in 3.0.13.
A few questions:
- Youāre on 3.1.10. Can you update to 3.1.14 and try again? @Maksim_Kochkin and @amatt said the issue is gone on 3.1.14, as long as youāre on macOS 26.4.
- Does the freeze happen only in the Agent Window, or also in the normal editor layout?
- Do you have any MCP servers set up? Please check
cat ~/.cursor/mcp.json.
One more thing, the logs show 427+ agent headers in LocalAgentStorage and 54 old databases. Try clearing agent history by deleting the contents of ~/Library/Application Support/Cursor/User/globalStorage/ (the folders with agent databases). This can reduce diff load.
Let me know how it goes on 3.1.14.
Iām partying on Version: 3.2.0-pre.22.patch.0 and living my best life now - thanks!
Iām on Version: 3.1.15 with no issues! Sorry, had to wait until a project was out.
I am still seeing this issue on 3.1.15
```
Version: 3.1.15
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0
```
Edit: Just saw that Iām on Tahoe 26.2 and not 26.4 - going to update and try again.
Iām on Tahoe 26.3.1 (a) and Iām still having the issue on 3.1.15.
Iām also facing the same issue. Have tried to reinstall, do all of the suggested tips with no luck.
No files load, agent keeps failing. Unable to use Cursor.
I feel like I should mention that I was seeing similar behavior after updating to 3.1.17 but thankfully closing cursor and restarting it again fixed the issue.
Not sure why the initial start after the update was wonky but thought Iād share in case anyone else sees the same.
Wanted to share a quick status update on this thread.
The fix for the freeze on Tahoe is in 3.1.14 and a few users above confirmed it, but the key detail is that it only works together with macOS Tahoe 26.4. On Tahoe versions below 26.4, the freeze can still happen (see @amatt in post #35, they had to update macOS to 26.4 before upgrading Cursor).
@leogou you are on 26.3.1. Try updating to 26.4 (Apple menu > System Settings > General > Software Update) and then install the latest Cursor (3.1.17 or newer). Let me know if the freeze is gone.
@lazer any updates after upgrading Tahoe to 26.4?
@gyasbic to dig in, please share:
- Cursor version: Cursor > About Cursor
- macOS version: Apple menu > About This Mac
- Your MCP config. In Terminal run
cat ~/.cursor/mcp.json - The log file at
~/Library/Application Support/Cursor/logs/main.log
@Betsy thanks for the note about 3.1.17. Good to know a restart after the update helped. If it happens again, send the logs and Iāll take a look.
If anyone on macOS 26.4 + Cursor 3.1.15+ still sees the freeze, please let me know and include logs. That would likely be a separate issue.
Updated macOS Tahoe to 26.4.1. the issue persists on Cursor 3.2.11 (latest). The error is less frequent than before, but still disruptive: it requires multiple reloads to resolve, and when that fails, rolling back to version 2.6.22 is the only reliable workaround.
Still having this issue. MacOS 26.4.1, Cursor Version: 3.2.11 (Universal). Was better with 3.1.XX.
Activity Monitor shows Cursor Helper (Renderer) CPU usage go to >100% when freezing.
Hey @samson-k, thanks for the report. Looks like this isnāt the same bug that was fixed in 3.1.14 (the one that fixed 3.0.13 on Tahoe), but a separate regression in 3.2.x. @leogou is seeing the same thing on 3.2.11 + 26.4.1.
To dig in, weāll need a few things:
- Log:
~/Library/Application Support/Cursor/logs/main.log(you can rename it to.txtto upload) - MCP config:
cat ~/.cursor/mcp.json(if the file exists, please post the contents) - Where exactly does it freeze: only in the Agents Window (new layout), or also in the normal editor layout?
- Are you using cloud agents, or is the repo linked to a GitHub PR?
- A screenshot of Activity Monitor during the freeze showing >100% CPU on Cursor Helper (Renderer)
As a workaround, based on what you said, 3.1.x was better. If you need to work ASAP, you can roll back to 3.1.17 (that branch seems more stable on Tahoe 26.4+).
@leogou if you can, please also share main.log and your MCP config from 3.2.11. Thatāll help confirm if itās the same issue or different ones.