Where do developer tools keep gigabytes?
Xcode, Docker, package managers, AI models and coding agents, folder by folder.
On a developer’s Mac, the space usually goes to a short list of folders. Each tool rebuilds or downloads most of its data again, so the safest way to clear it is the tool’s own command rather than deleting folders by hand.
Xcode and simulators
~/Library/Developer/Xcode/DerivedData— build products and indexes. Rebuilt on the next build. Delete per project, or the whole folder with Xcode closed.~/Library/Developer/Xcode/Archives— archives of builds you exported or uploaded. Keep the ones whose debug symbols you still need.~/Library/Developer/Xcode/iOS DeviceSupport— symbols for each iOS version of a device you connected. Downloaded again when needed.~/Library/Developer/CoreSimulator— simulator devices and their caches.xcrun simctl delete unavailableremoves simulators of runtimes you no longer have.
Docker and virtual machines
Docker Desktop keeps images, containers and volumes in one virtual disk inside ~/Library/Containers/com.docker.docker. It looks like a single large file. docker system prune removes stopped containers, unused networks and dangling images; add --volumes only if you are sure no volume holds data you need. OrbStack, Colima, Lima and UTM keep their disks in their own folders.
Package managers
- Homebrew —
~/Library/Caches/Homebrew;brew cleanup. - npm —
~/.npm;npm cache clean --force. - pnpm —
~/Library/pnpm/store;pnpm store prune. - pip —
~/Library/Caches/pip;pip cache purge. - uv —
~/.cache/uv;uv cache clean. - Gradle —
~/.gradle/caches; Cargo —~/.cargo/registry. node_modulesand build folders inside your projects, often the largest of all once you have many projects.
AI models
- Ollama —
~/.ollama/models;ollama listshows models,ollama rmremoves one. - Hugging Face —
~/.cache/huggingface; the Hugging Face command line lists and removes cached models (hf cache, orhuggingface-cli delete-cachein older versions). - LM Studio and similar apps keep models in their own folders, often 4–40 GB per model.
Coding agents
Coding agents keep session histories, caches and sometimes extra working copies of your projects: ~/.claude, ~/.codex, ~/.cursor and the app support folders of their desktop apps. Each session is small, but they add up over months, and worktrees made for parallel tasks can be full copies of a project.
Watching it instead of cleaning it every month
Diskdiary colors the disk map by content type, so build data, simulators, virtual disks and AI models stand out. It finds coding agents’ folders after the first scan and offers them as Favorites, and its history of folder sizes shows what grew since yesterday.
- Alerts: Control-click
DerivedDataor~/.ollamaand choose Alert… to be warned when it passes a size. - For your agent: Diskdiary → Connect an Agent… gives a coding agent a command line to the same history, for example
diskdiary changes --period weekordiskdiary history ~/Library/Developer, so it can tell you where its own gigabytes went.
Diskdiary doesn’t delete anything; it shows you where to look.