A lid-closed developer workflow for the MacBook

The problem with closing the lid

By default macOS sleeps the moment you shut the lid, which suspends whatever was running. For a long build, an agent run, or a local model, that means lost progress.

Developers want to treat the MacBook like a small server for a few hours: close it, walk away, and have the work still going when they come back.

Setting up the workflow

Start your task, whether it is a build, Claude Code, Cursor, Docker, or Ollama, then turn on keep-running mode and close the lid.

LidRun detects the watched tool and holds the Mac awake, showing status in the menu bar so you always know a session is active.

Pick battery thresholds for an early warning and for automatic sleep, and set a session timer so the run has a hard cap.

Letting safety decide when to stop

Every keep-awake decision is gated by battery and thermal state. If charge drops past your critical level, LidRun lets the Mac sleep instead of draining it to zero.

If thermal state climbs, you see it in the menu bar and cooling profiles respond within what the hardware allows. The goal is to help reduce risk, not to ignore it.

Keep the Mac on a hard, flat, ventilated surface and stay plugged in for long jobs.

To build this workflow on your own Mac, see the plans on /pricing or get the app from /download.

FAQ

Can I really work from a closed MacBook for hours?

Yes, with keep-running mode on, as long as battery and thermal state stay within the thresholds you set. When a limit is reached, LidRun lets the Mac sleep.

Which tools does this work with?

LidRun detects many dev and AI tools, including Claude Code, Cursor, Docker, and Ollama, plus common terminal jobs.

Is it safe to leave the lid closed?

LidRun uses battery and thermal thresholds to help reduce risk, but keep the Mac on a flat, ventilated surface and plugged in for long runs.