Storage

Storage shows what is taking up space and what you can reclaim. Use the disk explorer to look through your drives. For file cleanup, Pip scans the folders you have chosen and the repo roots of your running dev servers when you ask it to. The button names what it will look at: Scan D:\Code and 5 more.

What comes back is findings — node_modules for repos you have not opened in a year, target from Cargo, .next, build caches, 23 kinds in all — each carrying its evidence, one sentence per fact. They land in two tiers: provably regenerable (inside a git repo, ignored by git, manifest sitting beside it — arrives pre-picked) and needs your call (never pre-picked, collapsed until you look). A repo with a server running out of it is never suggested, whatever its size — and documents are never candidates.

Before file cleanup, you review a plan showing every path in full and the space it can reclaim. Approved files and directories move into quarantine on the same drive. They stay restorable for seven days, with a countdown on each entry. After that, Pip purges them and measures the space freed. This restore window applies to quarantined files, not cache cleanup commands.

Pip also measures supported package-manager and Docker caches. Where a supported cleanup command is available, you can select it, review the exact command and its scope, then approve Pip to run it. For example, Pip can run pnpm store prune to remove unreferenced packages and cached registry metadata.

These commands use the tool's own cleanup behaviour. They take effect when they finish, do not go through quarantine, and have no seven-day undo window. Review what will be removed and what would need to be downloaded or rebuilt before approving the plan.

The only figure Pip calls reclaimable is the space you would actually get back. That is not what Explorer shows: a pnpm node_modules can read as hundreds of megabytes while nearly all of it is hard-linked into the package store, and deleting it would free almost nothing. Pip measures the difference, shows the shared portion on the row, and offers supported commands for cleaning the store after you review and approve them. Files held in quarantine still occupy disk space and retain their links until they are purged.