Diskray

macOS reports “System Data” as one opaque figure with no breakdown and no actions. Diskray makes it legible: Xcode DerivedData, simulator runtimes, Docker images, APFS local snapshots, /private/var/folders, and the rest of the developer detritus that quietly takes up hundreds of gigabytes.

How it works

Everything cleanable is a spec-defined module — 31 are bundled — and each one reports a physical size, carries a safety class, and explains itself in plain language. Recommendations annotate rows but never pre-select them, so nothing is ever queued up on your behalf.

Nothing is deleted from the browsing view. Every action produces a reviewable plan showing full paths, physical sizes, safety classes, and the equivalent command line — the app teaches rather than hides. You confirm on the plan screen or nowhere.

Safety model

• Dry-run is the only path. Every action produces a plan you review first.
• Items go to the Trash by default; a hard delete takes a separate confirm.
• A never-blocklist — Keychains, Photos, Mail, Messages, /System — is compiled into both the app and its privileged helper.
• No auto-clean, ever. Diskray notifies at thresholds; it never acts unattended.
• It never claims reclaimed space it did not verify: it measures the actual free-space change and discloses any shortfall plainly.
• Every deletion is written to a local audit ledger before it happens.

Status

Pre-release. Milestones M1 to M7 of the v1 roadmap are complete and the first signed release is in progress. There is no download yet, and no public source repository yet. Both arrive together with that release.

It is plain SwiftPM with no Xcode project, so once the source is published, building it is two commands.

Licence

Diskray is licensed under the MIT licence, and that will not change. Its bundled module specifications draw on mac-cleanup-py (Apache-2.0) and kondo (MIT), whose notices ship with the app. Module specifications are declarative JSON validated in continuous integration.

The source repository is not public yet. It will be published, and the licence is already settled — see the note on status above.