Cursor last update freeze on macOS

Ariel_Coyant · April 8, 2026, 1:24pm

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

On request to agent to make changes in the code the IDE freeze

Steps to Reproduce

Open a project request to change someting to a file

Expected Behavior

make changes normally

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.0.13
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
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.3.0

For AI issues: which model did you use?

Auto

Additional Information

On reopen the project cursor freeze again
if run sudo rm -rf ~/Library/Application\ Support/Cursor
i can open again the project but on first iteraction with an agent, freeze again

i try also reinstall cursor, same problem.
Start to happends after install the last update

Does this stop you from using Cursor

Yes - Cursor is unusable

ruan_hc · April 8, 2026, 1:40pm

Same here.

deanrie · April 8, 2026, 1:41pm

Hey, thanks for the report. I see the screenshot with “The window is not responding”, this looks like a known issue with macOS Tahoe.

A few questions to narrow it down:

Do you have any MCP servers set up? Cursor Settings > MCP
What exact macOS version are you on? Apple menu > About This Mac
When Cursor freezes, open Activity Monitor and check if any Cursor processes are using a lot of CPU. A screenshot would be ideal.
Also check Console.app, there might be crash reports from Cursor.

While we wait for that info, try this workaround:

Launch Cursor from Terminal with cursor --disable-extensions, this will help confirm if extensions are the cause.
If that doesn’t help, try rolling back to an earlier version before 3.0.13. A similar Tahoe issue was fixed that way: Cursor Mac is not responding after update

Let me know how it goes.

ruan_hc · April 8, 2026, 1:55pm

Cursor’s settings are not opening and many features are frozen.
macOS Tahoe 26.3.1 (a)
No high CPU usage detected.
No crash logs in Console.

Disabling extensions did not help.

The only workaround for me was rolling back to version 2.6.22.

Ariel_Coyant · April 8, 2026, 1:58pm

Same spect and description like @ruan_hc

deanrie · April 8, 2026, 2:06pm

@Ariel_Coyant @ruan_hc thanks for the details. It’s clear now, this is a macOS Tahoe compatibility regression in version 3.0.13.

@ruan_hc, since Settings won’t open, can you check if MCP servers are set up directly? See if there’s a file at ~/.cursor/mcp.json or .cursor/mcp.json in the project root. If it exists, please share the contents, it’ll help narrow down the cause.

For now, the only working workaround is rolling back to 2.6.22, like you already found. I’ve passed this to the team, no ETA yet, but your reports help us prioritize the fix.

If either of you can grab logs from ~/Library/Application Support/Cursor/logs/ the latest main.log that would also help a lot with debugging.

Betsy · April 8, 2026, 2:07pm

Same here, except Tahoe version 26.1

Settings won’t open so have to roll back which gets me back up so I can work today.

Would my logs be helpful if I’ve already rolled back?

deanrie · April 8, 2026, 2:17pm

Hey @Betsy, yep, the logs will help even after a rollback. We need the main.log file from ~/Library/Application Support/Cursor/logs/. It should still contain entries from the 3.0.13 session. If that folder was kept during the rollback, the data should still be there.

Also, like for the other users, can you check if ~/.cursor/mcp.json exists via Terminal cat ~/.cursor/mcp.json. If the file exists, please share its contents.

Thanks for confirming it also reproduces on Tahoe 26.1, that helps narrow the scope.

Betsy · April 8, 2026, 2:27pm

Sure, where should we send them?

ruan_hc · April 8, 2026, 2:30pm

Here are my logs:

main.txt (1.9 KB)

Here are also my MCP Servers:

{
  "mcpServers": {
    "Sentry": {
      "url": "https://mcp.sentry.dev/mcp",
      "headers": {}
    },
    "context7": {
      "url": "https://mcp.context7.com/mcp",
      "headers": {
        "CONTEXT7_API_KEY": ...
      }
    }
  }
}

deanrie · April 8, 2026, 3:23pm

Hey @ruan_hc, thanks for the logs and MCP config.

I can see you have the Sentry and Context7 MCP servers set up, which might be related to the freezing. There’s a known issue where things can freeze when using the agent plus MCP servers.

Can you try this on version 3.0.13 before rolling back:

Rename the MCP config: mv ~/.cursor/mcp.json ~/.cursor/mcp.json.bak
If you also have .cursor/mcp.json in the project root, rename that too
Launch Cursor and try using the agent

If the freezing goes away without MCP servers, that helps narrow down the cause.

Also, in the logs I see detected slow close() operation with a database size of about 1,4 GB. That’s unusually large and could affect performance.

@Ariel_Coyant do you also have MCP servers? Check with cat ~/.cursor/mcp.json in Terminal.

For now, rolling back to 2.6.22 is a working workaround.

Ariel_Coyant · April 8, 2026, 3:28pm

there is my mcp, working fine now on 2.6.22

{
  "mcpServers": {}
}

Ariel_Coyant · April 8, 2026, 3:31pm

the problem is with the last 3.0.13 the previous 3.0.X versions works fine for me

deanrie · April 8, 2026, 3:48pm

@Betsy thanks for the logs. It’s pretty clear that at 09:58:51 all Cursor processes got SIGTERM code 15 and crashed at the same time: fileWatcher, renderer, shared-process, ptyHost. After restarting on 3.0.13, the extension hosts started crashing again a couple minutes later. On 2.6.22 everything is stable, you can see that in the logs.

One more thing, can you check your MCP config? In Terminal run:

cat ~/.cursor/mcp.json

If the file exists, please paste the contents here. This will help us figure out if the issue is related to MCP servers or if it’s just a regression in 3.0.13 on Tahoe. @Ariel_Coyant has an empty MCP config and sees the same bug.

Betsy · April 8, 2026, 4:06pm

File does not exist

TonyW · April 8, 2026, 4:44pm

Cursor is also freezing for me. It is happening every time I try using the agent window (“Layout: glass”). I am on Sequoia 15.7.1. It seems to be some performance limit.

I use a very vanilla cursor setup. My development workflow might be leaving large “diffs” in cursor’s working log from my past months of work that the new view is trying and failing to handle that - I’m not sure.

Closing the agents window and only using the text-editor window (including the agents tab/layout) is working without any issues.

lazer · April 9, 2026, 6:44am

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After update to 3.0.13, source control panel does not load (“No source control providers registered”), Extensions panel does not load (no error), terminals do not load (no error), AI chat does not function (stuck on “Waiting for extension host”)

Steps to Reproduce

Click “Install” when 3.0.13 update prompt comes up in Cursor IDE. Observe issues above on restart.

Expected Behavior

Source control panel loads, AI chat works, terminals load.

Operating System

MacOS

Version Information

Version: 3.0.13
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
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

Additional Information

Have had this happen on two separate Macs. Reinstalling cursor worked on one, not on the other.

Does this stop you from using Cursor

Yes - Cursor is unusable

cbusiness · April 10, 2026, 2:37am

Cursor also freezing for me on Sequoia 15.7.5. I also have a very basic setup and did not have any issues until the latest update. I can open basic .txt and .py files but unable to use .ipynb files which is what I primarily use.

This solution below worked for me:

Quit Cursor

rm -rf ~/Library/Application\ Support/Cursor rm -rf ~/.cursor
3. restart Cursor

paintoshi · April 10, 2026, 7:42am

Same here with 3.0.16 on Windows. It refuses to load my source control and terminal for random projects, some times not loading the chat history either. Some times it works to close the folder and re-open it, but it was too frustrating so rolled back to v2.6.22.

Maksim_Kochkin · April 10, 2026, 7:51am

Same, MacOS 26.4, all v3 Cursor versions don’t work (honestly, I tried only a couple), only rollback to 2.6.22 helps.

Topic		Replies	Views
After last update, stuck at "Waiting for extension host" Bug Reports installation , extensions , crashes	62	16509	April 9, 2026
Cursor keeps crashing - 2.6.11 Bug Reports crashes , macos	46	1709	March 27, 2026
Cursor is not usable after the last update Bug Reports installation , performance , crashes	53	2365	March 16, 2026
Cursor becoming unresponsive with longer chats Bug Reports	54	1111	September 2, 2025
Cursor version 2.5.22 is unusable Bug Reports early-access , performance , crashes , windows	9	462	March 19, 2026

Cursor last update freeze on macOS

Where does the bug appear (feature/product)?

Describe the Bug

Steps to Reproduce

Expected Behavior

Screenshots / Screen Recordings

Operating System

Version Information

For AI issues: which model did you use?

Additional Information

Does this stop you from using Cursor

Where does the bug appear (feature/product)?

Describe the Bug

Steps to Reproduce

Expected Behavior

Operating System

Version Information

Additional Information

Does this stop you from using Cursor

Related topics