Free Up Space on a Developer Mac
Find which tool caches and build leftovers fill your Mac, and get the space back without breaking a project or a running coding session.
Each article stands on its own, because which of these fills your disk depends on what you build and which tools you run. Start with the first if you don’t know yet; it ends by pointing you at the part you need.
Every article gives the steps to run yourself and a prompt for your own coding agent that measures and reports before anything is deleted. Every number comes from a real Mac, measured before and after.
7 parts · 2 published
- Part 1
What's Taking Up All the Space on My Developer Mac?
Find which developer tool is filling your Mac's disk, such as uv, Xcode or Docker, and which cleanup applies.
- Part 2
Why Is the uv Cache So Large on My Mac?
Coding agents fill the uv cache when they launch MCP servers with uvx; prune it safely and see how much disk you really get back.
- Part 3
Shrink Docker Desktop's disk on a Mac
Why Docker.raw looks like a terabyte, and what pruning actually gives back
Announced — not published - Part 4
Clear the npx directory that npm cache clean misses
Where npx keeps the packages it runs, and why the npm command leaves them
Announced — not published - Part 5
Find what Xcode's simulators and device support files are using
Simulator devices, runtimes and device symbols, including the runtimes a du of your home folder never sees, and how to tell which you still need
Announced — not published - Part 6
Remove build leftovers from projects you no longer work on
Find .build, node_modules and virtual environments in idle projects and clear them with each tool's own command
Announced — not published - Part 7
What AI coding agents leave on your disk, and what not to delete
Scratch checkouts and worktrees from coding sessions, and how to have the agent sort what is safe from what is still in use
Announced — not published