Why caffeinate isn't enough for closed-lid AI workflows
caffeinate is one of the most useful commands on a Mac: a single line that stops the machine dozing off while something runs. But the moment your workflow involves closing the lid on a long AI job, caffeinate quietly stops being enough. Here is why, and what closed-lid work actually needs.
What caffeinate actually blocks
caffeinate is a small, dependable macOS tool. Run caffeinate -i and it prevents idle system sleep; -d keeps the display on; -s holds the system awake on AC power; wrap a command with caffeinate -i make and the lock lasts exactly as long as that command.
For a long build or a download with the lid open, that is often all you need, and it costs nothing. There is no reason to reach for anything heavier.
The key detail is the word idle. caffeinate blocks the sleep that happens when you step away from an open laptop. That is one specific kind of sleep, not all of them.
Why a closed lid is different
Closing the lid triggers clamshell sleep, a separate macOS behaviour. Unless an external display, power, and input are driving a true clamshell desktop, the system suspends within seconds of the lid shutting.
caffeinate does not touch that path. You can have caffeinate running and still watch the Mac sleep the instant you close the lid, because the two are answering different questions.
So for the increasingly common case, start an agent or model run, close the laptop, walk away, caffeinate alone leaves the job suspended in your bag. The idle lock is held; the lid still wins.
Related guideClosed-lid mode on macOS, without a kextThe safe way to close the lid on an AI run
Keeping work running with the lid closed needs the documented pmset disablesleep toggle, which changes how macOS treats a lid close. It is a system-wide setting and asks for an admin password each time it is turned on.
Doing that by hand is easy to forget to undo. LidRun pairs the toggle so it is always switched back off on stop or quit, and on the next launch after a crash it detects a leftover setting and resets it. The reset happens when the app next opens, not the instant a crash occurs, which is worth knowing rather than assuming it is immediate.
On top of that it adds the guardrails a closed-lid run should have: a low-battery auto-stop, a thermal step-back, charging-only and session-timer options. None of that claims a Mac cannot overheat. A closed lid traps heat, and the honest rule is to keep a running Mac out of a sealed bag.
Using caffeinate and LidRun together
This is not caffeinate versus LidRun. caffeinate is excellent at the job it was built for, and plenty of workflows never need more than its one-liner.
If you keep the lid open, caffeinate -i is often the simplest answer. If you close the lid on long AI and dev runs and want battery and thermal guardrails around them, that is the gap LidRun fills.
Many people use both: caffeinate for quick command-scoped tasks at the terminal, LidRun for the unattended closed-lid runs where forgetting to undo a system setting actually matters.
A feature of the safe AI workload layer for Mac.
LidRun keeps your work running with the lid closed, with battery and thermal safety built in.
Frequently asked
Not on its own. caffeinate blocks idle system sleep, but a lid close triggers clamshell sleep, which caffeinate does not affect. You need the pmset disablesleep path for that.
Not at all. It is a reliable built-in tool and the right choice for many lid-open keep-awake needs. The point here is scope, not quality: it simply was not built to handle a closed lid.
It needs the lid-close behaviour changed with pmset disablesleep, that change reliably undone afterwards, and battery and thermal guardrails so a long unattended run does not push the hardware.
Yes. caffeinate and LidRun can sit side by side: caffeinate for quick command-wrapped tasks, LidRun for the closed-lid, unattended runs where safety and cleanup matter.