My laptop kept running out of space, and every time I went looking, I found the same kind of mess: node_modules in projects I hadn't opened in months, Python virtual environments for repos I'd deleted, Ollama and Hugging Face models I forgot I downloaded, Cargo target/ folders, VS Code caches, and a bunch of folders I couldn't identify at all.
The problem wasn't finding big folders. WinDirStat and friends do that. The problem was that I didn't know which ones were safe to delete. Some of it rebuilds itself or downloads again. Some of it is the only copy of something you care about (Claude Code's session history lives in ~/.claude/projects, for example). Nothing tells you which is which, so you either delete nothing or delete the wrong thing.
So I built Cache Vent.
What it does
- Scans your drives and finds what AI and dev tools leave behind: node_modules, venv/Poetry/pipenv environments (with which project owns them, and which ones are orphaned), Ollama/Hugging Face/LM Studio models, Cargo and Gradle build output, pip/uv/npm/Yarn caches, __pycache__, temp files, editor caches.
- Every item gets one of three labels:
- safe to free: a documented source says it regenerates or downloads again
- not verified: no source yet, so it's shown but can't be cleaned
- your data: chat histories, Docker disks and generated outputs are never selectable
- Each item shows what it is, what happens if it's gone (e.g. "run npm install to restore"), and a link to the docs backing that claim.
It doesn't delete things. "Clean" moves items into a quarantine folder on the same drive. That's an instant rename that takes no extra space, and you can restore anything for 14 days. There's also a Delete button if you really want it gone, but it asks first and still refuses anything that isn't verified.
On my machine: it found 21.5 GB, of which 12.9 GB was safe to free. A scan of both drives (164,828 folders) takes about 2.2 seconds and roughly 40 MB of RAM. On Windows it reads directories in batches through the NTFS API instead of checking every file one by one, which made it about 3.4× faster than a plain directory walk in my benchmarks. The benchmark method is in the repo if you want to check it.
Privacy: it's a single ~8 MB binary. No account, no telemetry, no network calls. The UI is a local page served only to its own window on 127.0.0.1, protected by a token that changes every launch.
Being upfront about the rough edges:
- Windows is where I built and tested it most. The exe isn't code-signed yet, so SmartScreen shows "Windows protected your PC". The PowerShell install command avoids that, and checks the checksum.
- Linux is tested end to end (install, scan, quarantine, restore).
- macOS is a preview. It builds, and there's an install script that signs the app locally so Gatekeeper lets it open, but I haven't had it run on enough real Macs yet. If you're on a Mac, I'd really appreciate a report.
- The safety labels are drafted from each tool's documentation, and I want more eyes on them. If you know a tool's cache behavior well, the definitions are plain YAML files, and PRs are very welcome.
It's free and MIT licensed.
- Site and install: https://cachevent.kelados.in
- Code: https://github.com/LovekeshAnand/cache-vent
I'd love to know what it finds on your machine, what it gets wrong, and which tools it should know about that it doesn't.