The safety governor: why LidRun won't keep a hot or idle Mac awake
Keeping a Mac awake is trivial. The hard part is deciding when it should be allowed to sleep again. A mac keep awake safety governor is the layer that watches battery level, thermal state, power source, and how long a run has been left alone, and lets the Mac sleep when a limit is crossed instead of pushing the hardware. It helps reduce risk on long, unattended runs. It does not eliminate it.
Why a wake lock with no guardrails is risky
A plain keep-awake tool answers one question: should the Mac stay on? For a presentation or a long read, that is the right and only question. caffeinate, Amphetamine, and KeepingYouAwake all do this job well, and for short interactive use you do not need anything more.
Long, unattended runs are different. A 40-minute cargo build is fine, but the same wake lock left on through the night will happily hold a Mac awake while the battery drains to zero, or while it sits in a warm spot with the vents half blocked. The tool has no opinion about any of that. It was told to stay awake, so it stays awake.
That gap is the whole problem. The moment you walk away from a job, the decision to keep running stops being yours and becomes the tool's. If the tool only knows one word, the answer is always yes.
What the governor actually checks
LidRun gates every keep-awake decision on four signals. Battery level: if charge drops past the threshold you set, it lets the Mac sleep rather than running the cell flat. Thermal state: if thermal pressure climbs too high, it backs off instead of holding the assertion through the heat. Power source: it knows whether you are on AC or on battery, so a run on mains and a run on the cell can be treated differently. And unattended time: if a run has been left alone past a limit, that on its own can end the session.
When any of those crosses a line, the governor does the same boring, safe thing. It releases the IOKit power assertion and lets macOS sleep the Mac the way it normally would. It is not overriding the protections the system already has. It is choosing not to fight them.
And it writes the decision down. Every safety event lands in the Activity Log, so when you come back to a Mac that slept early you can see why: charge floor, heat, or a run that simply ran long with nobody watching.
Related guideWhen your MacBook gets hot while codingLetting the Mac sleep is the feature
It feels backwards to call sleeping a feature of a keep-awake app. But that is the point of a governor. The value is not in staying awake forever; almost anything can do that. The value is in stopping at the right moment without you there to pull the plug.
Picture an overnight Ollama pull on battery in a quiet office. A naive wake lock holds the machine on until the battery is dead and the job died with it. The governor watches the charge fall, and when it hits your floor it lets the Mac sleep with the battery still healthy. You lost the run either way, but you did not run the cell down to nothing to do it.
Same logic for heat. If the chassis is getting hot faster than it should, continuing to hold the Mac awake is the wrong move, and the governor treats it as such.
What the governor can't do for you
Be honest with yourself about the limits. The governor reads the signals the hardware exposes and acts on the thresholds you set. It cannot feel the room. If you run a job on a bed, a couch, or inside a closed bag, you have blocked the airflow the cooling system needs, and no software setting fixes a physically trapped machine.
Airflow and placement stay your job. Run long workloads on a hard, flat, ventilated surface. Keep the vents clear. Stay plugged in for the big ones so battery is not even part of the question.
Think of the governor as a careful second pair of eyes on the numbers, not as permission to stop thinking about where the Mac is. It helps reduce risk within what the hardware allows. The rest is on you, and that is the honest version.
LidRun keeps your work running with the lid closed, with battery and thermal safety built in.
Frequently asked
It is the layer that gates every keep-awake decision on battery level, thermal state, power source, and how long a run has been unattended. When a threshold is crossed it lets the Mac sleep instead of holding it awake.
No. It helps reduce risk by backing off when thermal pressure climbs too high, but it cannot fix blocked vents or a Mac on soft furniture. Airflow and placement are still your responsibility.
Yes. Every safety decision is recorded in the Activity Log, so you can tell whether it was the battery floor, thermal pressure, or an unattended-time limit that ended the session.
Yes. The safety governor and the low-battery auto-stop are part of the free, unlimited basic keep-awake. They are never gated behind Pro.