Guides
Where your disk went, and how to get it back.
Each guide covers one place a developer machine quietly fills up: what is stored there, how to measure it with standard commands, how to clean it by hand without losing anything, and how lysosome does the same checks for you.
-
Clean up the git worktrees your coding agents left behind
Find the dormant git worktrees Claude Code, Cursor and parallel agents create, check which are safe to delete, and remove them without losing uncommitted or unpushed work.
.claude/worktrees/*~/.cursor/worktrees/*git worktree remove -
Find and delete old node_modules, target and .venv folders safely
Measure the node_modules, Rust target, .venv, .next and dist folders in projects you no longer touch, confirm git ignores them, and delete them so the next install or build recreates them.
node_modulestarget/.venv.nextdist -
Free up disk space from Xcode: DerivedData, simulators and device support
Where Xcode keeps DerivedData, iOS DeviceSupport, simulators, simulator runtimes and archives on your Mac, how to measure each one, and which are safe to delete.
DerivedDataiOS DeviceSupportxcrun simctl -
Find and remove local AI models: Ollama, Hugging Face and LM Studio
Where Ollama, the Hugging Face cache, LM Studio, PyTorch and Whisper store model weights, how to see what each model takes and when you last used it, and how to remove the ones you don't need.
~/.ollama/models~/.cache/huggingface~/.lmstudio -
Docker disk usage on a Mac: find it and reclaim it safely
Why Docker Desktop's disk image keeps growing on macOS, how to see what images, build cache and volumes take with docker system df, and which prune commands are safe to run.
Docker.rawdocker system dfbuilder prune -
Or let lysosome check all of it
One read-only scan covers every guide here, labels each item by how safe it is to remove, and cleans only what is clearly rebuildable. Free, open-source CLI; the Mac app is in free beta.
brew install lysosome-dev/tap/lysosomeDownload for Mac
Commands are for macOS unless noted; most work the same on Linux. Paths and sizes in examples are made up.