IMPORTANT: Cursor lag & unresponsiveness (AI works ok)

I’ve found that I’m certainly not the only one experiencing this, so I know that the problem isn’t my own machine.

I’ll leave this here so people know this keeps happening on newer versions too:

Follow up:

Deleting the entire chat and composer history DOES NOT fixes Cursor lagginess.
Same with deleting WorskpaceStorage.

Comments from the team or somebody responsible would be appreciated.

Follow up:

I tried everything I found at Cursor – Troubleshooting Guide

It got better, but it’s still largely unusable.

Hey, have you also tried reinstalling Cursor? What do you see in the system processes? Is Cursor using up a lot of resources? Have you also tried starting it in safe mode with the command: cursor --disable-extensions?

I’m having issues as well. I’m using vscodevim, running on Ubuntu. When scrolling, moving between lines, etc. I often get 1-2 second hangs. Today it seems to be worse than ever. I’m not sure if it’s from the update from today or if I’m building up history or what.

Same here! The interface lag (on latest version + current Linux Mint) is getting increasingly bad. There are 2-5 seconds delay when I write prompts.
This is really frustrating and a bad experience overall.

1 Like

This is likely due to terminal tool rendering:

new cursor version this morning slowed stuff down especialy claude-sonnet 4 - don’t you guys test?

I too am lagging like crazy, seems chat history is a big problem for cursor to still deal with.

I’m on an AMD Ryzen 7 9800x3d, 64gb of DDR5 @ 6200mhz
AIO everything, including GPU

and the lag is terrible. Once I restart my PC and re-open the project it’s a little more tolerable but overall, it’s so bad that i’ve just adapted to it.

Running cursor via this command fixed all my lag
“& “C:\Users[Username]\AppData\Local\Programs\cursor\Cursor.exe” --disable-gpu”

I tried deleting all chats, new account, all extensions, disabling extensions, freeing up programs, reinstalling cursor, installing an old version, clearing globalstorage, workplacestorage, all cache. After the above command everything was usable again.