Cursor is unusable, extremely slow since this morning

Im seeing this here. The last week on and off seems to be unusable. Plans and Agent builds taking 20 minutes for simple tasks. making it useless unfortunately. My Network diagnostic logs.

Cursor Network Diagnostic Results: gist:b816df357def2ada9f7c4ab50ca93e60 · GitHub

It seem to help a lot if I choose a model like GPT 5.4 or Codex 5.4 instead of Auto but in that case I run out of tokens quickly.

Version: 3.1.17

VSCode Version: 1.105.1

Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90

Date: 2026-04-19T19:33:58.189Z (1 day ago)

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

Thanks. The situation returned to normal on its own a few hours after my message.
So I’m all good now.

i was having the same lagging issue with typing and just switched my theme to a default one and it fixed it.

was using monokai pro before which i recently installed.

So i have been experiencing a slow UI experience since the start of the month too, e.g. when typing, deleting, selecting a new cursor position, a delay in UI feedback really.

Starting with `cursor --disable-extensions` doesn’t help, however when opening the process explorer its snappy again lol? E.g. deleting characters.

Macbook Air M3 2024 (15 inch, 24GB ram) - MacOS Sequoia

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
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 24.6.0

looks like switching to a new version does not solve this issue… it is like slow to hell too in my using version 2.6.20 bluh after editing and opening a bunch of files

same here. especially when doing grepping. it just stuck there for a long time.

I am literally asking it to open a simple adata file and read off the dimensions and it can’t do it. It also spent $20 in the past two days just trying to do this. This is unusable and unacceptable.

Hey, thanks for posting in the thread. About the latest reports:

@ricky_b, the “snappy when Process Explorer is open” symptom is interesting. This is often related to background throttling of Electron processes. To dig in, can you share:

  • A screenshot of Process Explorer Cmd+Shift+P > Developer: Open Process Explorer when it’s lagging. Which process is using CPU
  • Whether GPU acceleration is enabled: Cmd+Shift+P > Preferences: Configure Runtime Arguments, check if disable-hardware-acceleration is set
  • Does the lag happen right after startup, or does it show up after N minutes of work or after opening Y files
  • Are you using external monitors, or any display scaling

If you can, a short screen recording of the lag 5 to 10 seconds would really help.

@taliefirzen, “slow after opening a bunch of files” sounds like memory pressure or an extension memory leak. Run cursor --disable-extensions from Terminal, open the same set of files, and see if it still happens. If things are fine with extensions off, it’s likely one of them. Cmd+Shift+P > Developer: Show Running Extensions will show what’s using resources. Also share your macOS version and how much RAM your machine has.

@lsc04361, getting stuck on grep could be a known case with multi-root workspaces. Can you confirm:

  • Do you have a single folder open, or a multi-root workspace with multiple folders added via File > Add Folder to Workspace
  • Repo size roughly, files count or GB
  • Cursor version Help > About Cursor > Copy
  • If you have a Request ID for the stuck grep request, please share it chat menu top right > Copy Request ID

Since the thread has grown and the cases are different, if anyone has a stable repro, it’s easier to open a separate thread with specific symptoms and diag logs. We can move faster that way. Thanks for your patience.

Same issue. Reading extremely slow and absolutely unusable since yesterday

Experiencing the same issue. Chat input is laggy and generally the whole app is very, very sluggish. Cursor’s responses are slow. On an M4 Max MacBook Pro, 128gb ram, Tahoe 26.3.1. Not snappy when Process Explorer is open. Restarting helps a bit but it quickly becomes sluggish again. Render seems to be the culprit.

Version: 3.2.16 (Universal)
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
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: Darwin arm64 25.3.0

Hey Dean,

  • Version: 3.2.16
    VSCode Version: 1.105.1
    Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
    Date: 2026-04-28T21:07:47.682Z
    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: Linux x64 6.19.14-ogc1.1.fc44.x86_64

  • This happens both on Windows 11 and Bazzite

  • single root with multiple folders

Thanks for the info. This matches a known issue ERROR_EXTENSION_HOST_TIMEOUT that we’re currently investigating. The fact that it reproduces on both Windows 11 and Bazzite is an interesting signal and should help narrow it down. No ETA for a fix yet.

To dig deeper, try these in order:

  1. Reload Window in the error window (button on the right in the popup, or Ctrl+Shift+P > Developer: Reload Window). Sometimes the extension host comes back.
  2. Without extensions: run cursor --disable-extensions from a terminal and try the same prompt. If it works, the issue is likely caused by an extension (Jupyter, Remote-SSH, and MCP-related extensions are especially suspicious).
  3. Clear cache (if the steps above didn’t help):
    • Linux/Bazzite: rm -rf ~/.config/Cursor/Cache ~/.config/Cursor/CachedData ~/.config/Cursor/"Code Cache"
    • Windows: delete %APPDATA%\Cursor\Cache, %APPDATA%\Cursor\CachedData, %APPDATA%\Cursor\Code Cache

Also, if you can, please share:

  • The full Request ID (the screenshot is cut off at 861d5397-8b40-49ac-877b-3...)
  • Exported logs: Ctrl+Shift+P > Developer: Export Logs, then attach the zip to the post
  • How you installed Cursor on Bazzite (rpm-ostree layered, Flatpak, AppImage, or something else)

With the exthost.log logs, we can see if activation of a specific extension is crashing, which is often the cause.