Keeping Mac work alive without pretending awake means safe
A developer usually meets Mac power management through a simple need. A build, local server, download, or agent is still running, and idle sleep would interrupt it. The caffeinate command can be enough for that open lid case. Lid close is a different boundary. An idle sleep assertion does not mean the same thing as a closed display session, and a product should not blur the distinction. I built…
Developers often encounter Mac power management issues when a build, local server, download, or agent remains active while the system enters idle sleep. The caffeinate command addresses this concern, but lid close is a separate situation. Idle sleep does not equate to a closed display session, and companies must maintain a clear distinction.
Afterlid was created around three distinct states: Sleepy, Awake, and Always On. Sleepy follows regular sleep patterns, Awake prevents both idle and display sleep when the lid is open, and Always On applies to the closed lid mode with an off display. After activation, the focus shifts to handling potential issues. If the app crashes, the battery becomes low, the system faces thermal pressure, the app heartbeat stops, or after eight hours, Afterlid returns the Mac to normal sleep behavior.
The current implementation relies on a privileged helper and an undocumented macOS sleep setting. This highlights the importance of thorough testing and honest release notes. Founder notes that the product's recovery process is crucial, emphasizing that activation is a feature, but recovery is the product.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
