Why auto-quit should refuse unsaved work
An app that can close other apps has one job before it is useful: it must not throw away a document. Here is how Amhara draws that line.
The fear is rational
Anyone who has lost a save dialog to a force-quit knows why auto-close tools get uninstalled. The feature is only as good as the cases it refuses. If a utility cannot tell an idle browser from an unsaved Figma file, it does not belong on a working Mac.
Hide, then quit, with a list of things it will not touch
Amhara's auto-close is off by default. When you enable it, an idle app is hidden first, then quit after a buffer — not yanked out from under a cursor. A permanent exemption list includes Premiere Pro, Final Cut Pro, Logic Pro, and Finder: those never receive a close from Amhara, idle-based or manual. A warning tier (Figma, Photoshop, and similar) gets two minutes before a quit.
Separately, Amhara checks for unsaved documents in known editors before it closes anything. That check is not a screenshot of your screen and not a read of the file. It is the same class of Accessibility-backed inspection window managers already use to see whether a document is dirty.
You stay in control
Whitelist, snooze, and per-app delays exist because one global timer is a blunt instrument. If an app should never be touched, it never is. If you want the Dock quieter overnight and nothing else, that is a setting, not a personality change imposed by the product.