Cursor becoming unresponsive with longer chats

[DBACPhoenix]

Describe the Bug

I’ve gotten to the point that working with the Cursor chat is no longer viable. I could be working on a single issue, like an error that I want the agent to resolve, and the longer the agent works on it, the more frequently and longer Cursor becomes unresponsive. If it can solve it in one-shot then it doesn’t seem to happen, but if the agent needs to debug the error across multiple turns, the unresponsive behavior becomes unbearable.

This unresponsive behavior doesn’t happen when the Agent is working. The behavior only appears after the chat has completed. At that point, Cursor will have a cyclic behavior of unresponsiveness. Typical behavior is 10 seconds working correctly, followed by 5 seconds of unresponsiveness. This behavior loops.

If I restart Cursor, the unresponsive behavior doesn’t manifest. However, if I pull up my previous Agent chat, the behavior will start again. I don’t need to send a request, just pulling it up is enough to cause this to happen.

And to be clear, I describe this unresponsive behavior as a total hang/freeze of the Cursor client such that will not take any key or mouse input. Windows recognizes the unresponsiveness and can ask to wait or kill the client.

I run into this issue whether I’m running direct through Windows or through WSL. I’ve disabled extensions as well to make sure it wasn’t anything weird there.

Would love some official support on this. I’ve seen others in the past have this issue, but I’ve never seen it get resolved.

Steps to Reproduce

Create a long, multi-turn discussion with the agent.

Expected Behavior

Cursor should never become unresponsive

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.0 (user setup)
VSCode Version: 1.99.3
Commit: 410000a83355c025daba0c6156955bf08687d080
Date: 2025-07-23T05:57:24.496Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Yes - Cursor is unusable

[condor]

hi @DBACPhoenix and thank you for the detailed report.

Could you please check following for any errors shown and post them here?

Help > Toggle Developer Tools > open Console tab there

[deanrie]

Hey, does the same thing happen in other projects?

[DBACPhoenix]

I tried to isolate things this time, so I created a new project with an empty folder and prompted the Cursor agent the following:

Help me create a API that uses the Nylas API to capture incoming emails and use OpenAI to categorize them with appropriate labels.

Followed by this prompt to add a bit more to the conversation.

Both OpenAI and Nylas libraries should be used instead of making httpx calls. Also, break up the main.py to use a better project folder structure and have separate files for handling data models, fastapi entry point, main app, and services. The project will use UV to manage dependencies.

After everything was generated and accepted, I restarted Cursor and opened up the developer tools to monitor the console log and do a performance trace. At this point, all I did was click on files and scroll up and down.

No errors appeared in the console, however, Cursor became unresponsive 3 times in over a minute.

The large idle frame times (9.6s, 7.2s, 15.7s) were the moments when Cursor froze.

There are errors in the console when I’m generating code with the agent, but I didn’t want those to be confused with reasons why Cursor was becoming unresponsive. That is why I restarted Cursor, only showing the conversation history, navigating files, and scrolling through the content. Those are the only actions in which Cursor becomes unresponsive. If I close that past conversation, Cursor performs normally. So long as the conversation is closed, I’ve not observed any unresponsive behavior.

[vardiou]

Describe the Bug

Cursor consistently freezes every few seconds after a completion finishes from any “O3” or Claude 4 model (maybe with other models too, but i only use these ones). While the model is generating there’s no lag, but the moment the response ends the UI starts to stutter/freezing even if I’m idle, moving the mouse, typing, or just scrolling causes brief hangs. This keeps happening until I close and reopen Cursor (only works until I open the chat or prompt again). The freezes occur even with no extensions running, no file indexing in progress, and no additional chats open.

Steps to Reproduce

Open Cursor on Windows 11.

Start a new chat or open an existing one.

Send any prompt to an O3* model (o3‑mini, o3‑mini-high), Claude 3.5 Sonnet, or Cloud 4.

Wait for the model to finish replying, everything is smooth during generation.

As soon as the reply stops, try to scroll, type, or move the cursor in the editor or chat pane.

Notice the UI freezing for seconds to a minute, unfreezing, and then freezing again repeatedly.

Repeat with different projects/workspaces: same result. Rebooting and disabling extensions doesn’t help.

Expected Behavior

The editor and chat UI should remain fully responsive the whole time

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.0 (user setup)
VSCode Version: 1.99.3
Commit: 410000a83355c025daba0c6156955bf08687d080
Date: 2025-07-23T05:57:24.496Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Yes - Cursor is unusable

[yakovw]

I have the same problem, glad to hear I’m not the only one.

[deanrie]

Hey, we’ve rolled out a new update 1.3.2. Could you update and check if everything runs smoothly? I also think you need to enable early access in Cursor settings if it’s not already enabled.

[RoadkillRon]

Been happening to me, its really bad! I deleted all my chats, I have to constantly restart my computer because Cursor open dev server after dev server, just open one, it fails, its doesnt read that it fails, opens another one, and another one. It lies, it opens one on 3001, and one on 3002, then one on 3003, then runs some tests using 3000 (that isnt runnng because it crashed) and it says "Great, the server is running and everything is fixed! I can barley type, it hangs, and hangs every few seconds, it crashes constantly. Honestly, I can’t believe I still use it - it doesnt even write code that works! Every single thing it does sounds good, sounds right, but it codes errors into my code on a absolutely relentless pace! My env’s are blocked from the llm, it CONSTANTLY tells me there missing, goes around the rules and reads them anyway, creates new ones, edits existing ones, all while they are really there and accurate! This software is an absolute WASTE of time, money, energy, ect.
This is what I’m paying for, I’m actually paying my money for bad code, an IDE that I cant type in, that crashes! Got got NOTHING, Nothing but a bill for BuULLSHIT!

[vardiou]

Hey deanrie, thanks for the quick feedback!

I updated to 1.3.2 and Early Access is enabled here, but I still see the same behavior here, what I just noticed is a very specific behavior now.

If I have a chat opened and I do an Alt+Tab to leave and get back to cursor, the folders in cursor starts loading (the loading symbol appears in the folders) and that freezes the UI.

This happens every time i do an Alt+Tab with a chat window (that have been used) opened.

Note: I also tried with all extensions disabled and this behavior still happens

[deanrie]

Thank you for the details. Could you also try opening another project and check if the issue persists?

cc @andrewh

[vardiou]

Sure, I have lots of projects and it happens in all of them, this project is a new one that I started yesterday

[xmo909]

Constantly does it to me. Fresh projects, fresh agent chat; freezes after maybe 3 prompts, then just crashes as I’m doing something with no warning. Getting really bad and has been like this for awhile now. Makes doing anything a massive chore. I have to type prompts out in Notepad and paste them in once its unfrozen for the most brief period. I reopen the program after a crash, try running commands in the terminal and it crashes without warning. Absolutely unusable.

[amritashan]

Describe the Bug

After the update on 25th July, 2025 (Friday), Cursor has become extremely laggy and almost unusable.
It keeps freezing after every few seconds and when it comes to it applies all the actions, that have happened while it was frozen, at once.

Steps to Reproduce

1. Open Cursor IDE
2. Use it as usual - type, click, interact (no need to interact with the AI even)

Expected Behavior

Cursor should work lag-free

Screenshots / Screen Recordings

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.4
VSCode Version: 1.99.3
Commit: bfb7c44bcb74430be0a6dd5edf885489879f2a20
Date: 2025-07-29T03:55:23.805Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.8.0-64-generic

Additional Information

Look at the uploaded screen recording. each time it freezes and comes back, all the typings just get applied all at once.

Does this stop you from using Cursor

Yes - Cursor is unusable

[condor]

Hi @amritashan and thank you for the bug report.

Cursor should not be lagging like this, as there are no such reports yet on 1.3.4 we may need help narrowing down the cause.

Could you check if the same happens with Extensions disabled?
You can launch it with cursor --disable-extensions

Also have a look in Help > Open Process Explorer and post here the screenshot if it has something consuming unusual amount of memory or CPU.

[Oliver_Siegel]

I also find that cursor has gotten kinda sluggish in the past few days, maybe week.

Very similar as demonstrated by the OP in the video.

I’ve used the cursor IDE for several months with no issues, and in fact I really loved how fast it made my workflows. The cursor-tab suggestions are very useful and often incredibly accurate.

However, recently there would be several lags, when typing normally, without using the cursor-tab suggestions. It feels as if my actual cursor to type code is waiting for the cursor-tab to ping the LLM on the server or something. It’s kind of intermittent and hard to predict or reproduce, but it just happens during normal usage, drastically reducing the reactivity of the IDE. Even if only or a few moments, this is quite annoying.

This is separate, but could be related: Previously I’ve noticed that the chat prompt input field will be a bit laggy to type in. I’ll type my prompt, and sometimes it’ll be a few moments before the rest of my sentence appears. I felt like this was happening more often when the context window was already kind of full - so didn’t think much about it, because it wasn’t a big deal.

But lately, since this week, I’ve found that the regular IDE typing is laggy - that’s quite frustrating.

And what’s added to the frustration, is that my cursor-tabs haven’t been applied reliably anymore. Sometimes it would just type a regular tab, and continue showing the suggestion. I hit tab again, just to add another tab character to the code rather than to apply the suggestion…

I understand that when having multiple lines highlighted, the indentation takes precedence over the cursor-tab suggestions acceptance, when pressing the tab key on the keyboard.

But I am definitely in one line only… Something is making things laggy, and it’s disappointing because the speed was literally the best part about this software!

[bromanguy]

Having the exact same issue. It’s been really painful to work with lately.

[Ali_Sufiyan]

having the exact same issue and even though i posted another thread here if possible to run cursor on GPU because even my CPU is powerful enough but cursor is literally so laggy and worst, sometimes it forces me to switch to windsurf for basic things…

[webdo]

Same exact problem here, sometime the whole window just freezes for a few seconds when I click. When that happens, closing the app takes around 5 seconds and it says it’s waiting on UI and Remote Agent.

[ngynlaam]

Same here. My Cursor gets laggy whenever I Alt+Tab and type.

[condor]

Hi @webdo @Ali_Sufiyan @bromanguy @Oliver_Siegel Thank you for sharing your experiences here. It would be very helpful to know which version you are on so we can address the issues and launch bug fixes.