The cursor isn't working

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The cursor takes a very long time to complete even the simplest tasks.
It starts mapping out a plan of action, then freezes and does nothing.
Or it doesn’t even finish planning the next steps—it freezes halfway through a sentence.
It only works for 10% of requests, which makes the work more difficult. More time is spent on reloading
The problem has persisted for the last 3 days; I’ve updated the course, changed models, but nothing helps
Has anyone else encountered something like this?

Steps to Reproduce

Enter any task, and it starts

Operating System

MacOS

Version Information

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

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This looks like a client-side freeze. The backend is handling your requests fine and generating responses, but the UI hangs while rendering. This pattern is familiar on 3.2.x, the bugs are logged, but there’s no ETA for a fix yet.

To understand your exact case and link it to the right ticket, can you share:

  1. Request ID from the frozen chat: chat menu (three dots in the top right) > Copy Request ID
  2. Process Explorer during the freeze: Cmd+Shift+P > Developer: Open Process Explorer. Please send a screenshot with CPU/RAM for Cursor processes, especially extensionHost, ptyHost, and renderer
  3. Does it freeze only in Agent, or also in Plan and Ask?
  4. Does restarting Cursor help, even temporarily?

In parallel, please try:

  • Start Cursor with extensions disabled: run cursor --disable-extensions in Terminal. If the freezes stop, one of the extensions is likely the cause
  • If the agent thread has lots of messages or a big context, try starting a new chat. Long conversations can hit renderer memory
  • Check Activity Monitor and see if Cursor Helper (Renderer) is hitting a RAM limit

Send whatever you can collect and we’ll take a look.