I just launched Toolbox after repeatedly seeing cleanup apps tell me a folder is large without explaining what created it or how to undo a removal.
I built it around three constraints: scan only folders the user chooses, show evidence before cleanup, and keep recovery records for Trash-backed actions.
I m curious where trust still breaks down for you:
- What evidence do you need before deleting a path?
Hi Product Hunt,
I built Toolbox because I kept running into the same problem on my Mac: I could see that a folder was large, but I couldn't tell what created it, whether it was safe to remove, or how I would undo the cleanup if I got it wrong.
So I made the tool I wanted to use myself.
Toolbox has three main workflows:
- Install Trace compares filesystem metadata before and after a normal installer.
- Projects finds known rebuildable output only inside project folders you choose.
- Recovery keeps evidence for Trash-backed cleanup actions and checks paths before restoring.
It runs locally and doesn't require an account. There is no telemetry, privileged helper, automatic deletion, or malware verdict.
One honest limitation: Toolbox 2.0 is a stable product release, but it is ad-hoc signed and not notarized by Apple, so macOS requires the Open Anyway step in Privacy & Security. I included a SHA-256 checksum, and the source is public. Please don't disable Gatekeeper or remove quarantine attributes.
I'm looking for practical feedback from Mac developers. What evidence would you need before cleaning a path? Which confirmation or recovery step feels unclear? And which project artifact should Toolbox recognize next?
If you find a reproducible issue, please include your macOS version and Mac architecture, but not private paths or files:
https://github.com/thangldw/toolbox/issues
Thanks for trying it.