@Evan_Lee glad turning off HTTP/2 fixed it. That confirms it was a network layer issue. Since it’s fast again, I’ll mark this as resolved. If it comes back, ping me with a new request ID.
@f00z fair point. Here’s the deal with state.vscdb:
Don’t delete it outright. It stores your chat history and internal indexes. If you delete it, your chats can get stuck on Loading Chat… forever because Cursor can’t rebuild that index by itself. More details here: Deleting global state.vscdb causes infinite 'Loading Chat' in projects, history not recoverable without corrupted backup
What to try instead:
- Fully close Cursor and make sure no Cursor processes are still running
- Run a SQLite VACUUM on the file:
This compacts the database without breaking anything. Quick heads up, if the file is huge, some users say it doesn’t shrink much, so results can vary.sqlite3 "%APPDATA%\Cursor\User\globalStorage\state.vscdb" "VACUUM;" - If VACUUM doesn’t help, at least back up the file before deleting it, so you can restore it if needed.
About the general slowness like taking 3 minutes to close and UI freezes while the agent runs. A 10 GB state file can absolutely cause that. The team knows about the unbounded growth issue and it’s being tracked.
Can you also share your Cursor version and try turning off HTTP/2 like above? That might help with agent timeouts separately from the state.vscdb issue.