DevCleaner - Free the gigabytes your dev tools and AI apps hoard

@dawedeveloper Looks interesting. Will definitely check it out.

@vikramp7470 Thank you! Cursor is sneaky - it keeps a local index of your entire codebase that can balloon to gigabytes over time. And Ollama is the worst offender: a single model is 2–40 GB, and it never garbage-collects the ones you stopped using. That was actually the trigger for building DevCleaner - I opened Finder one day and just saw a huge ~/.ollama/models folder staring back at me. 😅

@dardaelliande 

110 GB — and Android Studio taking 52 of those is very on-brand. That tool's Gradle cache + SDK components + emulator images is a monster. Glad it could help.

And the storage tier math is exactly right. Apple's $200 jump from 512 GB → 1 TB is basically a multi-year DevCleaner subscription at a fraction of the cost. That framing is more useful than any benchmark I could show.

The Ollama granularity feedback is 100% valid and noted. You're right that all-or-nothing isn't good enough for models — they're not caches, they're assets you chose to download. The right UI is exactly what you described: expand the category, see each model with its real size, check off the ones you don't use anymore. That's a different interaction than "nuke the DerivedData folder" and it deserves its own flow.

It's on my list. No ETA I'd commit to publicly, but this comment is the kind of specific, reasoned feedback that moves things up the queue. Thanks.

@mohamed_hussein25 It varies a lot by stack - but here's what the data shows: Xcode developers are typically sitting on 15–50 GB in DerivedData + simulators alone, sometimes over 100 GB if they've been building for a year or more without cleaning. AI tool users (Ollama especially) often have another 20–80 GB in model weights they've forgotten about. npm/node_modules graveyards add another 5–15 GB if you have a lot of old projects.

We actually have a live counter on the homepage showing the total freed by everyone who's used DevCleaner - it's ticking up in real time today. The number that surprises most people isn't the total, it's how much comes from categories they'd never think to check (looking at you, iOS Simulator runtimes - a single old runtime is 7 GB).

Short answer: the median first-time clean is probably somewhere in the 20-40 GB range for an active developer. But I've seen screenshots from users clearing 200+ GB in one sitting. 😅

@therayess Ha, "vibe coder" — love it. And yes, build artifacts are the silent killers. DerivedData alone can quietly eat 50–100 GB without ever asking permission. The really fun part is that macOS's "free up space" suggestion will never point you at ~/Library/Developer — so most people don't even know it's there until they run du -sh ~/Library/Developer and have a small crisis. 😅 Thanks for the upvote, really appreciate it on launch day!

@sarveshsea Landfill with a keyboard" is the most accurate description of my machine pre-DevCleaner that I've ever read. Stealing that for the README. 😄 Thanks for the upvote!

@honza_vomacka This is exactly the reaction that makes building something worth it — you don't know the problem exists until you see the number. Glad it helped! 🙏

@harini_mukesh Thank you so much for support. And answer to your question...I don't know, because I have no info about what my users clean. The only thing what I can tell you is taht users save more then 1T of storage in 100 runs on their devices

- info from 17.6.2026

@christian_heiduschke That’s literally the story behind DevCleaner - I kept losing tens of GB to DerivedData and old simulator runtimes and wanted something that shows what is safe to delete before you touch it.

Glad it helped you find the culprit. If anything still feels unclear in the app, I’m around - and honest feedback always welcome.

@huxley_peckham Thank you so much Huxley! I love to hear some honest feedback if you have some time after usage of DevCleaner ;-)