Traces of uninstalled applications
Dragging an application to the trash leaves preference files, application support directories, caches and logs behind. These are located by association and presented together, which is the space most disks are actually losing.
Reports before it removes
Caches, build directories, archived downloads and simulator runtimes are listed with the capacity each occupies. Removal is confirmed per category; nothing is decided on the user's behalf.
Duplicate detection across the disk
Duplicate files are identified by content rather than filename, so copies that were renamed or moved are still recognised as the same file.
An explanation layer, not just a list
A recommendation layer served through CoralMeshAI explains what a given item is and whether removing it is safe — the question that actually stops people from cleaning a disk.
Always-on threat watch
A monitoring component runs alongside the cleaning functions rather than as a separate scan that has to be remembered.
Native, with no hidden business model
Written natively for macOS 15 and later. No bundled browser engine, no background service and no telemetry-based revenue model.
A separable cleaning engine
The cleaning logic is isolated as a standalone Swift package that builds and tests independently of the application shell.