# Request for official tool for Cursor to cleanup itself for its really hard burden and slow speed nowadays **URL:** \ **Category:** Feature Requests\ **Tags:** chat, performance\ **Created:** [May 22, 2026, 5:40am UTC](https://forum.cursor.com/t/request-for-official-tool-for-cursor-to-cleanup-itself-for-its-really-hard-burden-and-slow-speed-nowadays/161286 "2026-05-22T05:40:25Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![taliefirzen](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/taliefirzen/32/34303_2.png) [@taliefirzen](https://forum.cursor.com/u/taliefirzen)\ **Post date:** [May 22, 2026, 5:40am UTC](https://forum.cursor.com/t/request-for-official-tool-for-cursor-to-cleanup-itself-for-its-really-hard-burden-and-slow-speed-nowadays/161286/1 "2026-05-22T05:40:25Z")
### Feature request for product/service Cursor IDE ### Describe the request Cursor stores all chat, agent, and composer state in a single SQLite database (state.vscdb). This database grows without bound — there is no automatic pruning, no VACUUM, no lifecycle management. After weeks of normal use, the file balloons to multiple GB. The impact is brutal: - Every read/write traverses massive B-trees - WAL grows unchecked (checkpoint deferred for large DBs) - The main process writes GB/min to the WAL file - I/O storms cause CPU spikes, UI freezes, and terminal lag - ‘Taking longer than expected’ on every AI request - Eventually the editor becomes unusable — frozen for 10+ seconds between keystrokes This is not a niche issue. It hits every heavy user. The fix is mechanical: prune stale agentKv:blob:_, composer._, bubbleId:\* rows from cursorDiskKV, then VACUUM. This reduces a 5+ GB database to ~50 MB in seconds. REQUEST: 1. Automatic state.vscdb maintenance — prune stale entries and VACUUM periodically (or on startup) 2. Configurable retention — let users set how long chat/agent history is kept 3. At minimum, expose a manual ‘Clean Database’ command in the command palette Until this is built in, I wrote cursor-clean — a Python toolkit that diagnoses, cleans, and repairs the problem from the terminal: > **[GitHub - zhengchenliang/cursor-clean: Maintenance toolkit for Cursor IDE — diagnose,...](https://github.com/zhengchenliang/cursor-clean)** > > Maintenance toolkit for Cursor IDE — diagnose, configure, clean, and repair state.vscdb bloat It works. But users should not need a third-party tool to keep their editor functional. WHAT PROBLEM DOES THIS SOLVE: Cursor becomes unusable after extended use due to unbounded state.vscdb growth. Users on remote VMs, VNC setups, or machines without dedicated GPUs are hit hardest — the software rendering already pushes CPU, and the I/O storms from the bloated database make it unrecoverable without manual intervention. ### Operating System (if it applies) Linux ---
**Author:** ![Tom\_Coustols](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tom_coustols/32/97175_2.png) [@Tom\_Coustols](https://forum.cursor.com/u/Tom_Coustols)\ **Post date:** [May 22, 2026, 6:04am UTC](https://forum.cursor.com/t/request-for-official-tool-for-cursor-to-cleanup-itself-for-its-really-hard-burden-and-slow-speed-nowadays/161286/4 "2026-05-22T06:04:21Z")
hey, my solution to this was to create a copy, then directly ask cursor to check what was inside and go through with me and delete stuff that was safe.. when I had something I liked, just tell cursor to check if the file is still safe, if yes just put in back in the original file, and keep the old one just in case ---
**Author:** ![taliefirzen](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/taliefirzen/32/34303_2.png) [@taliefirzen](https://forum.cursor.com/u/taliefirzen)\ **Post date:** [June 14, 2026, 1:50am UTC](https://forum.cursor.com/t/request-for-official-tool-for-cursor-to-cleanup-itself-for-its-really-hard-burden-and-slow-speed-nowadays/161286/6 "2026-06-14T01:50:35Z")
Hi there, 3.7.36 is good thank you so much now I can play ---
**Author:** ![khara](https://avatars.discourse-cdn.com/v4/letter/k/b5a626/32.png) [@khara](https://forum.cursor.com/u/khara)\ **Post date:** [June 15, 2026, 4:35pm UTC](https://forum.cursor.com/t/request-for-official-tool-for-cursor-to-cleanup-itself-for-its-really-hard-burden-and-slow-speed-nowadays/161286/7 "2026-06-15T16:35:12Z")
yes please add 🙏 I have an agent manually clean db but it would be wonderful to have a setting for chat retention and to auto-clean. ---
**Author:** ![f3matt](https://avatars.discourse-cdn.com/v4/letter/f/a9a28c/32.png) [@f3matt](https://forum.cursor.com/u/f3matt)\ **Post date:** [July 7, 2026, 10:43pm UTC](https://forum.cursor.com/t/request-for-official-tool-for-cursor-to-cleanup-itself-for-its-really-hard-burden-and-slow-speed-nowadays/161286/8 "2026-07-07T22:43:36Z")
I had agents build a python script to cull Cursor’s database based on age of agent chat, pin/archive status, in-workspace saved plans, and anything that was referenced by documents. I ran that with Cursor closed, then reopened and ran `Developer: GC Agent KV Blobs.`(Yes, automatic backups, etc.) This cut my state.vscdb from 10gb to 500mb. This reeeeeeeeeealy should be a core feature. ---
**Author:** ![taliefirzen](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/taliefirzen/32/34303_2.png) [@taliefirzen](https://forum.cursor.com/u/taliefirzen)\ **Post date:** [August 6, 2026, 5:00pm UTC](https://forum.cursor.com/t/request-for-official-tool-for-cursor-to-cleanup-itself-for-its-really-hard-burden-and-slow-speed-nowadays/161286/10 "2026-08-06T17:00:16Z")
looks like in their recent version they still are disabled to handle long conversations and keep bloating the db to 20GB. Why Cursor keep its users in pain…