Provider catalogue

Providers are the scanners: each one knows where one family of disk usage lives, how big it is, and what cleanup is safe. devdoctor providers shows what is registered and available on your machine. Per-entry labels always win over the family default.

Safe — regenerable caches

ProviderCovers
uv-cache, pip-cache, poetry-cachePython package download caches (uv-cache asks uv cache dir where the cache is, and forces past the lock a parent uv run holds)
npm-cache, pnpm-store, bun-cacheJS package-manager stores
go-cachesGo build, test, fuzz, and module caches
nuget-cachesNuGet global packages, HTTP, temp, plugin caches
homebrew-downloadsCached Homebrew bottles
vscode-extension-downloads, cursor-extension-downloads, cursor-updater-cache, vscode-logs, cursor-logsEditor extension package downloads, Cursor's staged updates, session logs
pre-commit-cache, puppeteer-browsers, node-gyp-cache, electron-cache, opam-download-cache, google-updater-cacheTool download caches: hook environments, browsers, Node headers, Electron binaries, opam sources, updater downloads
gradle-cachesJVM build caches
chrome-cache, firefox-cache, arc-browser-cache, vscode-cache, cursor-cacheBrowser and editor caches
tiktoken-cacheTokenizer cache
playwright, docker-installerBrowser binaries for testing; Docker installer
tox-nox-environmentsGenerated tox/nox test environments

Reclaimable — rebuildable at a cost

ProviderCovers
dockerImages, containers, anonymous unused volumes (named volumes: dangerous)
docker-vm-disk, claude-vm-bundlesVM disk files
colima-vm-disk, colima-cacheColima (Lima) VM disk images (advice only) and downloaded base images
rustup-toolchains, nvm-node-versions, pyenv-versionsInstalled toolchains and language versions, one entry each; advice names the tool's own uninstall command
vagrant-boxes, steampipe-plugins, docling-cacheDownloaded boxes and plugins (advice), Docling models
editor-extensionsInstalled VS Code, Cursor and Windsurf extensions (advice)
codex-runtimes-cache, exo-modelsCodex CLI downloaded runtimes, exo model weights
git-worktreesLinked worktrees whose branches are fully integrated
time-machine-local-snapshots (macOS)Local snapshots; all-but-newest bundle plus per-snapshot entries
node-project-dependenciesnode_modules under common code roots
cargo-targets, cargo-dependency-cacheCargo build dirs; registry archives and git checkouts
terraform-workspacesPer-workspace .terraform directories (re-created by terraform init); the scan measures the plugin copies a shared TF_PLUGIN_CACHE_DIR would collapse
python-venvsVirtualenvs (rebuildable)
conda-package-cachesConda package caches
xcode-development-data (macOS)Derived data, device support, archives, unavailable simulators
coresimulator-caches (macOS)The iOS Simulator's dyld shared caches, rebuilt on the next simulator boot
android-sdk-storage, android-project-buildsSDK images, emulator storage, Gradle build dirs
maven-repoLocal Maven repository
slack-service-workerSlack cached web assets
ollama, huggingface-hub, lm-studio-models, and other *-models / *-cache AI providersLocal model weights and inference caches

Dangerous — may hold user data

ProviderCovers
codex-sessions, claude-code-sessionsAgent transcripts in age buckets; only buckets past the 90-day retention floor are offered, one session at a time
opencode-sessionsOpenCode's session database, counted by age read-only; never edited
large-filesUnusually large files — user data until you say otherwise
downloads~/Downloads
conda-environmentsNon-base Conda environments (may hold your work)
open-webui-dataOpen WebUI application data

yarn-cache is safe, except project-local Zero-Install caches, which are dangerous advice instead.

Platform notes

Next: Safety model · Tutorial · CLI reference