Cursor window frozen

after upgrading to 3.0.16, and enable Agents Window, the editor window often looks frozen. Checking in task manager, I can see 20+ processes created, and CPU usage is above 20% sometimes

I have run cursor –disable-gpu but not helpful(I dont have GPU)

Where does the bug appear (feature/product)?

  • Cursor IDE

  • Cursor CLI

  • Background Agent (GitHub, Slack, Web, Linear)

  • BugBot

  • Somewhere else…


Describe the Bug
The UI appears very busy, and responses from model is very slow. I ask questions in both chat and agents windows. sometimes the answer never comes back.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …start the app(sometimes show agents window and main window, sometims only show agents window and main editor window doesn’t show up)

  2. ask a question


Expected Behavior
expect smooth ask/answer and execute my commands


Screenshots / Screen Recordings
below is the task manager when I run no task at all in cursor


Operating System

  • Windows 10/11

  • MacOS

  • Linux


Version Information

  • For Cursor IDE: Menu → About Cursor → Copy

  • For Cursor CLI: Run agent about in your terminal

Version: 3.0.16 (user setup)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
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: Windows_NT x64 10.0.26200


For AI issues: which model did you use?
not AI issue.


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable

  • Sometimes - I can sometimes use Cursor

  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.


Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!


Expected Behavior
What is meant to happen here that isn’t working correctly?


Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)


Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)


For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…


Additional Information
Add any other context about the problem here.


Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

Hey, thanks for the report. I see the Task Manager screenshot with 18 Cursor processes, and two of them are each using about 23% CPU while idle. That’s definitely not normal.

To figure out which component is causing the load, I’ll need a couple things:

  1. Cursor Process Explorer: Ctrl+Shift+P > Developer: Open Process Explorer. It shows what those processes are, like extensionHost, renderer, ptyHost, etc. Please share a screenshot from there.

  2. Test without extensions: run cursor --disable-extensions from the command line. If the freeze goes away, it’s likely caused by an extension.

  3. Test without Agents Window: try disabling Agents Window and switching back to the normal layout. Does the freeze still happen?

  4. Windows Defender: add your project folder to exclusions. On Windows this is a common cause of slowdowns: Problem with slow performance in Windows

Also, how big is the workspace you have open?

Let me know the results and we can decide the next troubleshooting steps.

Where does the bug appear (feature/product)?

  • Cursor IDE

Describe the Bug

After updating Cursor from version 2.5 to 2.6/3.0, the editor starts showing many small white dots/visual artifacts across the interface. The issue appears only in the newer versions and disappears when I downgrade back to Cursor 2.5. It looks like a rendering or graphics glitch rather than a project-specific problem.


Steps to Reproduce

  1. Install Cursor 3.0.16 on Windows 11.
  2. Open the IDE normally.
  3. Observe the interface after launch.
  4. White dots / visual artifacts appear across the screen.
  5. Downgrade to Cursor 2.5 and reopen the same setup.
  6. The issue no longer appears.

Expected Behavior

Cursor should open normally without visual artifacts, white dots, or rendering glitches.


Screenshots / Screen Recordings


Operating System

  • Windows 10/11

Version Information

IDE:
Version: 3.0.16
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
Layout: glass
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: Windows_NT x64 10.0.26200


For AI issues: which model did you use?

Not applicable — this appears to be a rendering/UI issue, not an AI/model issue.


For AI issues: add Request ID with privacy disabled

Not applicable.


Additional Information

The issue started after upgrading to Cursor 2.6 / 3.0.16. Cursor 2.5 works correctly on the same machine with the same project and environment. This strongly suggests a version-specific rendering bug. The problem appears as white dots/visual artifacts in the IDE UI.


Does this stop you from using Cursor?

  • Sometimes - I can sometimes use Cursor

Hey @Abubakar_Hassan, I see the screenshot. This is a known issue with GPU rendering in Chromium and Electron on Windows. We’ve had a few similar reports, and they were all fixed the same way.

Try turning off hardware acceleration:

  • Ctrl+Shift+P > Preferences: Configure Runtime Arguments
  • Add:
    {
      "disable-hardware-acceleration": true
    }
    
  • Fully close and restart Cursor

If that doesn’t help, update your GPU drivers. In a similar case Cursor Visual IDE Breaking Bug, updating the NVIDIA drivers fixed it completely.

What GPU do you have, and what driver version are you on? Let me know if the workaround helped.

I added "disable-hardware-acceleration": true in argv.json , fully restarted Cursor, and the white dots / visual glitch issue is now gone. It looks like the problem was related to GPU rendering on my machine. Thanks for the help.

Hi,

I added “disable-hardware-acceleration”: true in argv.json, restarted Cursor fully, and the issue is now fixed. The white dots / visual glitch no longer appear on my side.

Thanks for the help.

Best,
Abubakar

This project just starts, and only has less than 3000 lines of python code.

the top process seems to be a2a-server

disable-extensions seems improved. but I do need extensions. please help to identify the offending extension

screenshot is attached(This tool should have an export report function, screenshot is not cool enough to capture history.)

how can i disable Agents Window?

I dont have GPU, and above arguments doesnt help too

@deanrie is it still under investigation? I cannot use cursor for several days already

@deanrie I’m hitting the same issue that @Ron_Yan has reported. (I see that this thread has sprouted a few different unrelated issue reports; so it goes.)

Note that the editor window is not hung; it remains usable, although the hung agents window prevents the IDE from exiting without Force Quit – and, of course, background agents are unavailable unless I navigate to the website.

The new Agents Window hangs 100% of the time for me after a few seconds of being open. Processs Explorer screenshot below w/ window [2] (Cursor Agents) spinning at 100-200% of CPU.

The behavior reproduces even if I --disable-extensions. Windows is N/A. My workspace is medium-sized, perhaps 2,500 files.

System Info

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.3.0

Screenshot

Hey, I’ll reply to both. The issues look similar, but the causes are different.

@Ron_Yan, in your Process Explorer the top process is:

c:\Users\client6\.cursor\extensions\google.geminicodeassist-2.77.3-universal\agent\a2a-server.mjs - 11% CPU, 425 MB

That’s the Google Gemini Code Assist extension. Its a2a-server runs as a separate agent and often conflicts with Cursor Agent. Try disabling or uninstalling that extension Extensions > ms/google.geminicodeassist > Disable, then restart Cursor. I think CPU usage should calm down after that.

To switch from the Agents Window back to the normal layout:

  • Cmd+Shift+N

@xeger-ck, your case is different. window [2] Cursor Agents by itself is running at 108% CPU, so it’s not an extension. A few questions:

  • The Request ID from the stuck Agents window right click in chat > Copy Request ID, if Privacy Mode allows it
  • Does it reproduce if you open Cursor on an empty new workspace without your 2 500 files
  • After it hangs, do ptyHost and extensionHost also stay high in Process Explorer, or only window [2]

Workaround for now: don’t open the standalone Agents window, use the inline Agent in the main window you already have Layout: editor. If the Agents window is already stuck and blocks you from closing the IDE, Force Quit is unfortunately the only way out. This is a known separate bug on macOS.

Hey @Ron_Yan, in order.

About the delay: fair point. 5 days between replies is a long time, sorry. This thread grew into a few different bugs, and I missed replying to you directly.

On the main issue: you disabled Google Gemini Code Assist. Did the freeze and high CPU go away, or can you still reproduce it? In your Process Explorer, a2a-server.mjs from that extension was using 11% CPU and 425 MB, so after disabling it things should look noticeably better. If the freeze is still there, please share a fresh Process Explorer screenshot and we’ll check what’s at the top now.

About the Agents Window switching back to the classic layout on Windows:

  • Ctrl+Shift+N toggles between Agents Window glass and the normal editor layout

After that, in About you’ll see Layout: editor instead of glass.

On the fact that this toggle isn’t obvious: agreed. I’ll pass this feedback to the team. Right now it’s not in a visible place in the UI, and that’s a real problem if the mode causes freezes and you want to exit it quickly.

Let me know how performance looks now after disabling the extension.

Why haven’t I received a response or had my bug report resolved? Could you please send me your email address? There’s a major bug that I can’t directly explain.

all good for me now

@Ron_Yan, awesome, glad it cleared up. If it comes back, reply in this same thread.

@jojolionss, to avoid mixing a few different bugs in one thread (we already have Windows freezes, visual artifacts, and the Agents Window hanging on macOS here), please open a separate topic in Bug Reports: Bug Reports - Cursor - Community Forum

Please fill out the bug report template with what exactly is happening, repro steps, your Cursor version (About Cursor > Copy), your OS, and screenshots or a video. Without those details, we can’t dig into a “major bug.” If it’s related to your account or billing and you’d rather not post publicly, email [email protected].