While working with cursor agent (specifically Gemini 3) after a long iteration, the screen became black and completely unusable. Only a few random words are still visible.
I had to force-quit the application in order to close it.
Reopening the app solved the problem.
Hey, thanks for the report. This looks like a rendering corruption issue. Since it happened only once and restarting fixed it, let’s gather some diagnostic info in case it happens again:
If it happens again, please capture:
Console logs: Help > Toggle Developer Tools > Console tab (screenshot any errors)
Check extensions: CMD+Shift+P > “Developer: Open Extension Monitor” to see if any extensions are using excessive resources
The agent - Gemini 3 Pro - was running for about an hour in iterative chat mode. I do notice that this agent is much more verbose than other agents, resulting in much longer contexts and chats, even in a short session.
Oops I did it again. Well, actually you did.
Black screen one more time.
This time no agent is running and actually no run/debug process is running as well.
I have just applied the OpenAI Codex plugin and then opted for restarting the IDE.
That’s all.
Following advices here: Toggle Developer Tools is useless since the entire screen is black. See attached image.
Same for the Extension Manager. It isn’t visible.
—–
Once restarted again and the problem is gone I see nothing special in the Extensions page.
There are multiple warnings and errors on the Developer console.
A few are listed here:
workbench.desktop.main.js:8991 Error warming cursor server for bc-6d881dc1-b49b-4c95-b339-c98776ec1c08: ConnectError: [invalid_argument] Error
workbench.desktop.main.js:55 ERR [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (/Applications/Cursor.app/Contents/Resources/app/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:531:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:“{\“error\”:\“Trace spans collection is not enabled for this user\”}”}
workbench.desktop.main.js:6299 [Extension Host] [otel.error] {“stack”:“OTLPExporterError: Bad Request\n\tat IncomingMessage. (/Applications/Cursor.app/Contents/Resources/app/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:531:35)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)”,“message”:“Bad Request”,“code”:“400”,“name”:“OTLPExporterError”,“data”:“{\“error\”:\“Trace spans collection is not enabled for this user\”}”}
workbench.desktop.main.js:6995 [transport] Connect error in unary AI connect ConnectError: [invalid_argument] Error
at t (workbench.desktop.main.js:6331:410245)
at async Object.getBackgroundComposerChangesHash (workbench.desktop.main.js:565:74406)
at async workbench.desktop.main.js:8994:36066
at async fTo._fetchOptimizedDiffDetailsAndUpdateImpl (workbench.desktop.main.js:8994:37121)
Object
workbench.desktop.main.js:8994 Optimized diff batch update failed: ConnectError: [invalid_argument] Error
at t (workbench.desktop.main.js:6331:410245)
at async Object.getBackgroundComposerChangesHash (workbench.desktop.main.js:565:74406)
at async workbench.desktop.main.js:8994:36066
at async fTo._fetchOptimizedDiffDetailsAndUpdateImpl (workbench.desktop.main.js:8994:37121)
Hi, just wanted to post that exactly the same happened to me and I had an agent running for hours. Initially I could see some parts of the app, but after moving it around and resizing the app window it went totally black and unusable. I had to restart. I don’t have any screenshots since it went completely black.
I restarted the app anad it seems it’s working, but not sure for how long.
