On DB growth: as of 3.21.4 there’s still no automatic retention or pruning for the local chat database, so with heavy usage it keeps growing. This is a known issue we’re tracking, but I can’t share an ETA yet. Cleanup is manual for now:
Fully quit Cursor and reopen it.
Command Palette Ctrl+Shift+P → Developer: Delete Old Chats…, pick a cutoff in days (pinned chats are kept).
Command Palette again → Developer: GC Agent KV Blobs. Wait until you see the completion message.
Fully quit Cursor again (Reload Window isn’t enough) and reopen. The file only gets compacted on disk after a full quit.
On crashes with code 133: that’s the renderer process for a window getting killed under memory pressure. Very long conversations with lots of file edits can trigger it. What helps right now:
Start a new chat every few hundred messages instead of keeping one endless thread.
Accept or reject the agent’s edits as you go. Every unreviewed diff keeps a file in memory, and hundreds of those add up fast.
To confirm there isn’t something else in your case, please send:
The size of state.vscdb before and after the cleanup above (Windows: %APPDATA%\Cursor\User\globalStorage, Linux: ~/.config/Cursor/User/globalStorage).
The completion message from Developer: GC Agent KV Blobs (it includes total / live / deleted).
The exact crash dialog text next time, plus the block from Help > About from that machine. In your post the version block looks like Windows 10, but the form is marked as Linux, so I want to confirm which machine we’re looking at.
The Cursor account email on that machine, if it’s different from your forum one.
Share those details and we’ll check whether this matches the known pattern or if there’s something else going on.