Yeah, I always use a new chat for new questions/asks
The cursor stays unresponsive in the same way.
Have a look through the trouble shooting guide
Does this happen on a previous version?
Describe the Bug
Fairly often—on average every few minutes—the cursor freezes for a few seconds and nothing can be done during that time. This issue has been present from version 1.3 up to 1.3.7. I’m using it on Windows 11, nothing unusual besides that.
Steps to Reproduce
- use cursor as editor.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.3.7 (system setup)
VSCode Version: 1.99.3
Commit: 5d56108ff2401c28f239aa2a527ef424ce7719a0
Date: 2025-07-31T04:16:31.276Z
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
No - Cursor works, but with this issue
Hi,
I’m on Windows 11, I have updated Cursor to v1.3.8 (user setup), and I am still experiencing major lag when using Cursor (slow and laggy scroll, very long search…).
- With GPU acceleration enabled, it is more my browser and other apps which become laggy.
- When I disable GPU acceleration, the browser is fine—but Cursor itself becomes slow and unresponsive.
Note: I use it with WSL and with Capacitor JS.
Just adding my case to the list. Is it possible to disable indexing, or limit it ?
Thanks!
1 Like
I upgraded to 1.3.8, but my issue is still not resolved. Cursor lags tremendously.
Version: 1.3.8
VSCode Version: 1.99.3
Commit: a1fa6fc7d2c2f520293aad84aaa38d091dee6fe0
Date: 2025-07-31T21:41:43.219Z
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-71-generic
I have switched back to VSCode… and VSCode has been buttery smooth, with the same set of extensions and settings (which were imported to Cursor when i first installed it).
2 Likes
Thank you all for the latest reports. forwarded the info to our engineers.
1 Like
I’ve been experiencing the same, but I don’t want to just confirm the issue. I think I have details for the engineers that may be valuable:
I have a suspicion that the lag is coming from indexing the code. (Needs confirming!)
If you chat with the Agent and include images in the chat (e.g. take a screenshot and paste it into the chat context), the issue get worse.
Seems to persist even with extensions off (albeit, I haven’t tested this extensively).
However, I think this is a clue.
If the indexing operation could be sent to the background or handled async to rendering the screen this might relieve the issue a bit.
I’ve just been really keen to pay attention to the specific moments when the lag occurs.
It’s namely in moments when core components of the code change that would require a re-index of the code and updating the local index.
If this can be confirmed, it may help the team in identifying how this can be fixed to make sure Cursor can remain usable while indexing.
Just some thoughts…
EDIT:
Version: 1.3.8
VSCode Version: 1.99.3
Commit: a1fa6fc7d2c2f520293aad84aaa38d091dee6fe0
Date: 2025-07-31T21:41:43.219Z
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.6.58
Also: I regularly go thru and delete old chats to keep the cache clean.
However, regardless of zero chat history or not, the lag persists. This is what leads me to believe it may be on-index rather than any other cause (e.g. extension or huge chat history).
I also have started a habit of cleaning up chats across all projects, not just the active project.
I’ve also stopped running more than 1 Cursor window unless I really need both windows open (e.g. working on front-end stuff + back-end stuff).
EDIT(2):
Version: 1.3.9
VSCode Version: 1.99.3
Commit: 54c27320fab08c9f5dd5873f07fca101f7a3e070
Date: 2025-08-01T20:15:21.999Z
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.6.58
Soooo…. 
1.3.9 just came out in the few mins its taken me to publish this – let’s see how it goes!
2 Likes
It’s lagging horribly for me. It doesn’t matter if the chat is long or not. I also get terrible lags pasting anything in the chat window.
1 Like
This has been happening for me forever, it’s always the amount of data in the chats. The only way I can fix it which is just temporary of course is to either delete all the db files and start it up again, or by deleting all the previous chats including the current one and starting a new chat.
I’ve had reports open for this for many months , maybe even a year, it has to do with whoever programmed it making too much happen in the main v8 thread which blocks user input and eventually crashes (while the rest of the application runs fine in other threads). Also the poor storage method of chats and tracking lines by serializing json in a single row in the sqlite db and it reads and updates this every minute which lags out the whole application for increasing amount of times as it goes on. Apparently not an easy fix. I was thinking of moving the state.vsdcb to a ramdisk possibly to speed it up although i’m on nvme so it shouldn’t really matter.
Making a new chat temporarily fixes it but it eventually builds up to where making a new chat doesn’t help and you have to delete all the previous chats or delete all the installttion folders and resintall (don’t need to touch anything in your workspace folder though). You’ll lose all the checkpoints and stuff but it’s worth it to clear the lag
I also noticed even on a complete new install, some of the data in the db is installed on the cusrsor servers and gets repopulated, so they might have to look into that.
I wrote a script to prune the db which seems to help
1 Like
I’ve had this issue when - having many chats open in the new chats tab - and for me doing the following works :
note it does not clear your chat history.
2 Likes
I was forced to completely clear my installation and start over as the app was freezing every couple of seconds, it became completely unusable. Seems to be fixed but ofcourse I’ve lost history and pretty much everything (not my codebase obviously)
1 Like
@pepeday thank you for the update. We are indeed working on improvements and will release them as soon as they are ready.
1 Like
After a terribly laggy session, mine was stuck on this today for a while when trying to close it… Like a good 5-10 seconds. I feel like this is related…
Please try Cursor Settings > Beta > Update Access: Early Access