Anysphere Extensions (Remote SSH, Python, Dev Containers, WSL, C/C++/C#)
Describe the request
As Im heavily using Anysphere’s Remote-SSH extension, I notice that whenever Cursor has a new update, it installs a new commit folder into the .cursor-server/bin/linux-x64/ folder.
As time goes by, this folder was getting bloated. Each new cursor-server version takes about 400Mb, which is a lot.
Would love to request a feature that cleans up stale build (such as checking if a commit is too old, or not used for a while), then rm -rf that commit folder
Thanks for the suggestion! We already have some cleanup going on.
On each connect, the Remote-SSH install script keeps the 5 newest builds per platform folder (e.g. linux-x64, sorted by most recently used), skips any that look like they’re still running, and moves the rest into a .stale-builds-trash folder.
That trash is then deleted by a detached background process, so it never blocks your connection. It also cleans up older top-level build folders from before we switched to the per-platform layout.
So stale cursor-server builds should already be getting cleaned up automatically.
Hi Colin, thanks for reaching out. That helps me understand a lot.
To answer your question, I only see my cursor-server builds pile up to 5 max. Never exceed 5.
Still, on avg, each build is about 400Mb. And its data in CachedVSIXExtensions also tag along with each existing builds. So the amount of consumed storage is quite substantial.
Is there any config that I can set to reduce this number of builds, let’s say from 5 to 3 or 2, instead of relying on the hardcoded “5”? If there is no such config currently, I would love to see it become reality.