Your Mac is full of things you never chose — caches, simulators, old libraries, a toolchain from a project that died. Lastre shows you what each one is, where it came from and when you last used it. Then you decide.
brew install betancur/lastre/lastreFree and open source. macOS 14+. No account, no admin password, nothing deleted on its own.
Depth is time, thickness is size. Hover a layer — that is the whole app.
That is what a disk report says about an iMovie library. To turn it into a decision, you had to:
~/MoviesSix steps to answer a one-second question: what is this, and do I need it? Lastre exists to remove that trip. It shows the clips inside — without opening iMovie — and the date you last opened the library. The number becomes a decision.
Any disk tool can tell you what is big. The question is whether you still need it — and that answer lives somewhere different for every kind of thing. Lastre asks the right source for each one.
Repository keyba on main
Last commit June 24, 2026
2 commits not pushed · 1 file changed — they live in the project, not in this folder
From git. The warning nobody else gives.
Your projects' minimum iOS 17.0 (Affirmio, keyba) · 18.2 (Sinfonia)
Can run on iOS 18.5 5 of 6 projects
Devices on it 13, none ever started
From your Xcode projects and simctl.
Came from buzz.xyz
Last opened July 26, 2026
If you trash it only by downloading it again
From the file itself. Each download, one by one.
node_modules isYou don't need explanations, you need evidence next to the size — and the exact command when the Trash is not the right tool (xcrun simctl runtime delete …, brew cleanup). Lastre shows the command. You run it.
Your disk fills with things an AI created for you, and nobody told you what they are. Every row has a human title and one plain sentence: what this is, where it came from, what happens if you trash it. Commands you can paste into Claude and ask.
Cleaners earn distrust by doing things you didn't ask for. Lastre is built on the opposite bet: it is useful precisely because it is restrained.
simctl or brew, you get the exact text to copy. You stay in charge of your terminal.Most tools answer how big. The one that matters is do I still need it.
| Lastre | DaisyDisk | CleanMyMac | OnyX | Mole | |
|---|---|---|---|---|---|
| Shows why: last use per kind of thing | yes — git, simctl, Spotlight, your projects | size only | size and age | no | no |
| Decides for you | never | no | yes, Smart Scan | presets | yes, a "safe" tier |
| Asks for admin password | never | no | yes | yes | for system items |
| Deletes permanently | never, Trash only | yes | yes | yes | partly |
| Price | free, MIT | $10 | subscription | free | $19 app |
From each product's own site, August 2026. Tell us if something changed.
Signed and notarized by Apple. Opens like any app. Updates itself when you say so.
Requires macOS 14 Sonoma or later. On first launch macOS asks once whether Lastre may read Downloads — the only folder it needs permission for.
or with Homebrew
brew install betancur/lastre/lastre
Drag to Applications. That's it.
It cannot delete anything permanently, it never runs with elevated privileges, and it never executes commands. The worst it can do is move something to the Trash because you asked it to. The code is public.
Because the questions that matter — is this project dead? do I still need iOS 17? — depend on context no app can have. A tool that guesses eventually deletes something that mattered. Lastre would rather show you the last commit, the date and a thumbnail, and let you take one second to decide.
That nothing on your Mac records when that thing was last used — for example the simulator's system cache. Lastre says so instead of inventing a date. "Never used" and "no project uses it" are different, and it tells them apart.
Because hiding 149 GB would be dishonest. You deserve to know where your disk went, even when the right move is to leave it alone.
APFS frees space asynchronously, and local Time Machine snapshots can hold the blocks for up to a day. Lastre shows both numbers — what is free now and what macOS can still purge — so the two never look like a bug.