Cursor has grinded to snail speed. A simple prompt takes 30 mins to run

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Starting from around 3 days ago, my Cursor has grinded to a near halt. Even a simple prompt takes forever to generate. I have tried the solutions like disabling HTTP/2, running a simple prompt, and starting Cursor without extensions. Nothing works. Every prompt takes forever to run. Cursor has become extremely slow all of a sudden.

Steps to Reproduce

Every single prompt runs extremely slowly

Expected Behavior

Prompt should execute quickly

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

2.2.20
Windows 11
I have also tried 2.0.xx

For AI issues: which model did you use?

Auto or GPT 5.2 or Claude. Nothing works

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes
2

Same issue here, no matter which model I choose. How is it going for you?

2 Likes
3

yes, almost all of the models, mostly Auto

1 Like
4

Hey, thanks for the report. The issue with hanging on “Planning next moves” is a known bug we’re actively investigating. Many users have started reporting it in the last few days.

Similar reports: Planning next moves stuck

In the meantime, try this:

  • Start a completely new chat (not just clearing the current one - a new one)
  • Fully restart Cursor IDE (not just closing the tab)
  • If you’re using Agent mode, try switching to Ask mode or vice versa
  • Also try closing the project, opening an empty window, and sending a request. Does the speed return? If yes, reopen your project and check again

If the issue persists, let me know.

2 Likes
5

yep same issues

3 Likes
6

I’m getting the same issue!

1 Like
7

it’s not juts the ““planning next move” that’s stuck, every change is slow, typing is slow, the entire IDE’s responsiveness is sluggish at best, even after restarting the PC. I will try a fresh agent to see if resolved.

8

I realized that RAM usage increases over time (memory leak?) I recommend that you kill the cursor processes from time to time, and especially the cursor server if you work remotely

10

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.