You start a long build, a video export, a big download, or an overnight backup, walk away, and come back to find it stalled or dead. The culprit is almost always the same: macOS decided the Mac was idle and put it to sleep. Here is why that happens, and how to stop it for good.
macOS sleeps on idle, not on “nothing important is running”
The key thing to understand is that macOS watches for user activity - keyboard, trackpad, mouse - not for whether real work is happening. After a few minutes with no input, it starts powering things down to save energy, even if your CPU is pegged running a compile.
There are actually several separate timers:
- Display sleep turns the screen off.
- System idle sleep suspends the whole machine.
- Disk sleep spins storage down.
A long task that does not touch the input devices looks, to the system, exactly like a Mac sitting untouched on a desk. So it sleeps.
Why background jobs are especially vulnerable
Some tasks make it worse by spending most of their time waiting:
- A dev server or watch process idles between file changes.
- A download waits on the network.
- A backup waits on disk and on the destination.
- An AI agent pauses between steps while it thinks or calls a tool.
Low CPU use reads as “idle” to macOS, so these are the tasks most likely to be interrupted - exactly the ones you least want to babysit.
The role of App Nap and Energy Saver
Two more settings pile on:
- Energy Saver / Battery settings control how aggressively your Mac sleeps, and they are usually more aggressive on battery than on power.
- App Nap can throttle apps that appear idle in the background, which can slow or stall long jobs even before full sleep.
And one hard rule worth knowing up front: closing the lid sleeps the Mac regardless of what is running, unless you are on power with an external display attached (clamshell mode). No amount of “prevent idle sleep” changes that - see keeping your Mac awake with the lid closed.
How to stop it: from quick to permanent
There are three levels, depending on how often you hit this.
1. One-off: the caffeinate command
macOS has a built-in command that blocks idle sleep. Wrap the job you care about and the Mac stays awake for exactly as long as it runs:
caffeinate -i make
caffeinate -i npm run buildThis is perfect for a single command you run from the Terminal. The full caffeinate guide covers every flag.
2. Blunt: change your sleep settings
You can set the Mac to never sleep in System Settings, or with pmset from the command line. It works, but it is a global, always-on change: your Mac now stays awake for everything, all the time, and you have to remember to switch it back. That is a battery and wear trade-off you rarely want.
3. Automatic: keep awake only while your work runs
The trade-off most people actually want is: stay awake while the task is running, then sleep normally when it is done. That is what AwakeMate is built for. You tell it which apps and tools matter - Xcode, ffmpeg, a backup app, an AI agent - and it holds the Mac awake only while they are active, then steps aside. It even recognises CLI agents installed through npm or pip that otherwise show up as node or python, and it can sleep the moment a tool goes idle, so a build that finishes at 2am lets your Mac sleep at 2am.
Because it uses the same power assertion as caffeinate, it never edits your saved Energy Saver settings - normal sleep resumes the instant your work is done.
The short version
Your Mac sleeps because it measures your activity, not your work. For a single Terminal command, caffeinate -i <command> is the quickest fix. For anything you do regularly, an automatic keep-awake app saves you from both forgetting to turn it on and forgetting to turn it off.