Developer files
Finds dependency folders, build output and caches across every project, and says what each one is.
Get your disk back. See exactly why.
A developer-first disk-cleanup app and command line for macOS. It explains why your disk is full before it touches anything.
THE HEADLINE
6.2 GB → 295 GB
Free space on one MacBook after a single scan
$ plumb scan ~/code
▸ Build folders … 939
▸ Rebuildable … 398 GB
▸ Largest … .next 52 GB
✓ Documents touched → 0
01 · The problem
Developer Macs don’t fill up with documents. They fill up with things that can be rebuilt: .next and .turbo folders, Rust targets, iOS and Android builds, node_modules in worktrees, caches and Docker images. General cleaners either miss them or offer to delete things they can’t explain.
02 · What I built
Finds dependency folders, build output and caches across every project, and says what each one is.
Shows images, volumes and build cache, and how much each one takes.
Lists what’s running on which port, so a stuck dev server is one click away.
A visual map of where the space has gone, plus leftovers from apps you’ve removed.
Notices when a folder starts growing fast, before the disk fills.
The SwiftUI app and the plumb command line share one engine, so scripts and the app always agree.
03 · Key decisions
Everything is sorted into Safe, Check first or Your call, with the reason in plain words. Your call items are never ticked for you and go to the Trash.
A build folder is only suggested if it hasn’t changed in two days, no dev server is running, it’s a name tools always generate, it isn’t a link and git ignores it. Every check runs again just before removal.
04 · Stack
05 · Results
Next case study · 03
Proofly.ng
I design and build developer products end to end.