Hey, this looks like a known issue with the Glass agent window. The window crashes the renderer during initialization, most often because too many MCP servers start up in parallel right when you open it.
To confirm this and try a workaround:
Open Cursor Settings > MCP & Integrations and temporarily disable all MCP servers.
Restart Cursor and try Cmd+Shift+N again.
If the window opens reliably with MCP disabled, that’s the cause. Then you can turn servers back on one by one to find the problematic one, or just keep only the ones you need.
Also, can you share:
How many MCP servers are configured?
If you have a crash report from ~/Library/Logs/DiagnosticReports/ with Cursor or Electron in the name around the crash time, please attach it. It’ll help our engineers.
We’re tracking this bug on our side, but I can’t share an ETA for a fix yet. Let me know how it goes with MCP disabled.
Hey, thanks for testing that and for the screenshot. Renderer process crashes on macOS usually don’t show up in ~/Library/Logs/DiagnosticReports/, so it makes sense that folder is empty. If turning MCP off didn’t help, it’s probably a different type of the Glass renderer crash. Let’s collect a bit more info to narrow it down:
Crashpad minidumps
Please check ~/Library/Application Support/Cursor/Crashpad/completed/. You should see .dmp files created around the time of the crash. If you find any recent ones, zip them and attach them.
Renderer logs
In any Cursor window that still works, open Help > Show Logs or run Cmd+Shift+P then Developer: Open Logs Folder. In the latest session folder, grab renderer*.log and main.log from around the crash time and attach them.
Quick isolation tests
Do each test fresh, and restart Cursor between tests:
Launch from Terminal with extensions disabled using cursor --disable-extensions, then try Cmd+Shift+N.
If it still crashes, try a clean profile using cursor --user-data-dir=/tmp/cursor-test --extensions-dir=/tmp/cursor-ext-test and reproduce. This helps us tell if it’s workspace or state related, or a deeper rendering issue.
Dev Tools when it crashes
Open a working window, then go to Help > Toggle Developer Tools. Open the Console tab and leave it open, then trigger Cmd+Shift+N. The new window inherits Dev Tools. If you see errors before it dies, please screenshot the Console.
Extensions list
Also helpful is a list of your installed extensions. Run Cmd+Shift+P then Extensions: Show Installed Extensions.
This bug is on our radar, but there’s no ETA for a fix yet. The logs above will help us confirm which version of the crash you’re hitting.
