Editor extensions
--editor-ext removes superseded VS Code and Cursor extension versions. When an extension updates, the
old version directory often stays on disk. On a machine with many extensions and a few years of updates this
accumulates to hundreds of megabytes.
linux-cleanup --editor-ext
The two conditions
A version directory is a candidate only when both hold:
- A newer version of the same extension exists — the current version is never a candidate
- That older version has been idle for
--daysor more (default 100)
The second condition was added in 1.2.1. Before that, supersession alone was enough, which removed old versions you had loaded recently. Output shows per-version idle days, so you can see why something was kept.
What it does not touch
- The current version of any extension
- Extension settings, keybindings, or workspace state
- Anything in
~/.config— that whole tree is protected - Extensions in an editor other than VS Code and Cursor
After running it
If VS Code shows a missing-extension banner, reload the window: Ctrl+Shift+P → Developer: Reload
Window. The editor is holding a reference to a directory that no longer exists.
If an extension is genuinely gone — which would mean the "highest version" detection mis-identified the current one — reinstall it and please report the bug:
code --install-extension <publisher>.<name>
Expected reclaim
The size depends on the superseded versions installed on this machine. Use a scan to inspect the current directory before deciding whether to clean it.
In the walkthrough and all-safe
Runs as step 4 of the guided walkthrough, and is included in
--all-safe since it only ever removes regenerable, superseded copies.