What DevCleaner scans

Toolchains and IDEs

The classics that quietly accumulate tens of gigabytes of build artifacts and package caches:

• Xcode, including DerivedData (Compilation Cache, Module Cache, Symbol Cache, SDK Stat Caches, and per-project folders), Source Packages (per-project checkouts), archives, DeviceSupport, build logs, the Swift Package cache and old Swift toolchains (keep-newest)
• iOS simulators via the Simulator Slimmer: every CoreSimulator device grouped by runtime (size, last launch, installed app names in the caption), superseded runtime images, and one-click removal of unavailable simulators — all via simctl, never rm
• Android Studio and the Android SDK, including Application Support caches, logs, indexes, emulator snapshots (without deleting whole AVDs), keep-newest SDK platforms / build-tools / NDK / cmdline-tools, old emulator system images, and old Gradle wrapper dists
• JetBrains IDEs (IntelliJ, PyCharm, WebStorm and the rest), including Application Support caches, logs, indexes, Toolbox download cache, old Toolbox IDE apps, and orphaned older major App Support folders
• VS Code caches, crash reports, workspace storage and file history
• CocoaPods, Homebrew (download cache and brew cleanup --prune=all), npm / Yarn / pnpm / Bun (including npx cache, npm logs and keep-newest Playwright/Electron/Cypress/Puppeteer browser binaries), Python (pip, uv caches and keep-newest uv toolchains), Flutter (pub cache, SDK caches, Dart analysis and old FVM SDKs), Rust (registry cache, rustup temp and old rustup toolchains), Go (build cache and tool caches), Maven, .NET / NuGet, Composer and Unity
• Version managers — nvm, fnm, asdf, mise, pyenv, rbenv and SDKMAN (keep newest + current per tool)
• Developer Logs in ~/Library/Logs for simulators, Docker, Colima, OrbStack, editors and Homebrew
• System Temp (7+ days) — age-gated cleanup of /tmp and /private/var/tmp only (never /private/var/folders)
• Custom folders you add yourself

AI coding tools

The newest disk hogs. DevCleaner separates throwaway caches from things you might want to keep:

• Claude (the desktop app and the Claude Code CLI)
• ChatGPT, Gemini CLI, Codex CLI, Cline, OpenCode, Freebuff / Codebuff, Aider, Continue, Goose, Copilot CLI, Cursor, Windsurf, Antigravity, Zed, Kiro and Deno
• Ollama, LM Studio and ML Caches (Hugging Face / PyTorch)

Editor and app caches are rated SAFE. Downloaded LLM model weights in Ollama, LM Studio, Hugging Face and PyTorch are rated WARNING and are never pre-selected, because re-downloading them is slow. Session transcripts and workspace storage are opt-in too.

Docker and containers

DevCleaner reads sizes straight from Docker, OrbStack and Colima, and can clear:

• The build cache
• Dangling and unused images
• Stopped containers
• Unused volumes

Container data lives inside a VM disk (~/Library/Containers/com.docker.docker for Docker Desktop, ~/.orbstack for OrbStack). DevCleaner surfaces where that data lives and uses docker … prune — the safe way to reclaim space.

Project intelligence

Beyond package-manager caches, DevCleaner can surface disk hogs tied to your repos:

• Ghost Projects — per-project DerivedData breakdown for deleted or stale Xcode workspaces (free)
• Project Artifacts — stale node_modules, Pods, build folders, and Python .venv / venv under configured project roots (free to discover; manual delete via Quick Clean)

How ratings work

Across every tool, the same three levels apply: SAFE regenerates for free, WARNING is slow to rebuild, and DANGER can break your setup. Read more in how DevCleaner keeps you safe.

FAQ

How many tools does DevCleaner scan?

30+ developer tools including Xcode, Docker, npm, Homebrew, Gradle, AI coding agents, local LLMs and system temp.

Are all categories safe to delete?

No. Each category is rated SAFE, WARNING or DANGER. Only SAFE items are pre-selected.

Will DevCleaner scan custom folders?

Yes. Add custom scan paths and project roots in Settings → Folders.