How to Use Claude to Find What's Actually Eating Space on Your Computer

Start a new Claude session and make the safety rule explicit: you want help investigating first, not deleting first. The point is to have Claude explain what is large, what it likely contains, and what is usually safe to remove before any destructive command gets suggested.

Help me investigate what's taking up storage on this Mac. Start by identifying the biggest directories in my home folder. For each large folder, explain what it likely contains, whether it's usually safe to delete, and what questions I should answer before removing anything. Do not suggest destructive commands until we've reviewed the findings.

Once Claude gives you commands, run them in Terminal and paste the results back in. This gives Claude real local information to work from instead of vague guesses.

Pro tip: The built-in Mac storage screen is useful for broad categories, but it often misses the real story. The problem is usually not one huge file. It is a pile of medium-size directories, old dependencies, and app caches that add up fast.

If you do any kind of web development, node_modules is usually one of the first places to check. Old experiments, abandoned repos, and half-finished client work can each carry hundreds of megabytes or several gigabytes of dependencies.

Scan my dev folders for large node_modules directories. Show me the largest ones, where they live, and when they were last modified. Separate them into: 1. likely safe to remove because the project looks old or inactive 2. review manually because the project may still be active Explain your reasoning for each one.

This is one of the easiest cleanup wins because you are usually deleting installed dependencies, not your source code. If a project is old and you need it later, you can reinstall everything with npm install.

Pro tip: If you do not know which projects are still active, ask Claude to interview you. It can walk through the list one folder at a time and help you decide what is stale.

After node_modules, move on to package-manager and tooling clutter. Homebrew is a common offender because it accumulates old downloads, outdated package versions, and dependencies you no longer need. Docker can do the same thing with images, containers, and build cache.

Explain how to safely clean up Homebrew on this Mac. Tell me what old versions, caches, or unused dependencies are taking space, what the normal cleanup commands would do, and which ones are low-risk versus which ones need manual review first.

Help me find Docker files, images, and caches that are taking significant space on this Mac. Show me what is low-risk to remove, what needs review first, and how much space each cleanup might save.

The habit that matters is asking Claude to preview the impact first. Do not run cleanup commands just because they look standard.

App cache is another easy place to reclaim space, and the Claude cache can get surprisingly large. During setup for this guide, the cache had grown to around 15 GB, much of it tied to Claude Cowork usage.

Open the Claude desktop app and click Help > Troubleshooting > Clear Cache and Restart. You can also click Delete Cowork VM Bundle and Restart. That deletes virtual coding sandboxes that Claude Cowork has used.

Do not click Delete Cowork VM Sessions and Restart, as that will delete all your Claude Cowork threads.

Pro tip: This same logic applies to other local AI apps too. If you use ChatGPT desktop, Codex, or similar tools heavily, their local caches may be much larger than you think.

The bigger win here is not just getting space back once. It is creating a repeatable cleanup workflow so you do not end up rage-deleting files the next time your disk fills up.

When you finish the audit, ask Claude to turn your process into a reusable Claude skill.

You can also ask Claude to create a checklist in a markdown skill file so you can manually track the same process every month.