Closed-lid mode on macOS, without a kext
Plenty of tools promise to keep a MacBook running with the lid shut, and it is fair to ask how. Here is the honest version of how LidRun does closed-lid macOS without a kext — what the toggle actually is, why it always undoes itself, and the tradeoffs you should know before you trust it.
What closed-lid mode actually toggles
When you close a MacBook lid, macOS normally sleeps within seconds unless an external display and input device are driving a true clamshell desktop. To keep work running with the lid shut and nothing else attached, something has to tell the system not to sleep on lid close.
LidRun does that with the documented pmset disablesleep toggle. There is no kernel extension, and no DriverKit driver pretending a display is connected. It is the same supported power-management lever Apple ships, flipped on for the duration of the session and off again afterward.
That choice is deliberate. A kext or a fake-display approach can break with an OS update and demands deep system trust; the documented toggle is narrower, more predictable, and does exactly one thing — it tells macOS not to sleep when the lid closes.
Why it always undoes itself
A toggle like this is only safe if it is always reversed. The danger is leaving a Mac that physically cannot sleep — that is how a laptop ends up cooking in a bag. So LidRun always pairs the enable with a matching disable: turn it on to start the session, turn it back off when you stop, when you quit, and again when the app relaunches and reconciles state.
But apps crash, and a crash could in theory leave the toggle stuck on. That is what CrashGuard is for. On the next launch LidRun reconciles the disablesleep setting back to a safe state, so a crash does not leave the Mac unable to sleep. The invariant is simple: the enable is never left dangling.
This is also why LidRun shows a heat warning and asks for admin authorization before it enables closed-lid mode. Changing this setting needs admin rights, and the warning exists because a closed lid traps some heat by design — you should opt in knowing that, not stumble into it.
Guide associéUn flux de travail développeur couvercle fermé pour le MacBookWhy this means a direct DMG, not the App Store
The pmset disablesleep toggle needs administrator authorization and is not Mac App Store sandbox-safe. The sandbox the App Store requires would not let LidRun flip that setting, so closed-lid mode simply could not exist inside it.
That is why LidRun ships as a notarized, direct DMG rather than through the App Store. It is a tradeoff: you download and install it yourself instead of getting it from a single store listing. On first launch outside the App Store you may need System Settings, then Privacy and Security, then Open Anyway — or on older macOS, right-click and Open.
Notarization means Apple has scanned the build for malware even though it is not store-distributed. So you still get that check; you just opt into a capability the sandbox would forbid.
Honest tradeoffs before you rely on it
No software toggle changes physics. A closed lid restricts airflow over the keyboard deck and traps some heat, so a heavy job behind a shut lid runs warmer than the same job with the lid open. LidRun's safety governor watches battery and thermal state and will let the Mac sleep if pressure climbs too high, which helps reduce risk — but it does not make the heat go away.
Placement still matters more than any setting. Run it on a hard, flat, ventilated surface, never on a bed or in a closed bag, and prefer mains power for long closed-lid jobs so battery drain is off the table.
If all you need is the screen to stay on, you do not need closed-lid mode at all — a plain keep-awake assertion is enough and avoids the admin prompt entirely. Reach for closed-lid mode only when you genuinely want to shut the laptop and walk away.
LidRun garde votre travail actif capot fermé, avec une protection batterie et thermique intégrée.
Questions fréquentes
No. It uses the documented pmset disablesleep toggle — no kext and no DriverKit display-faker. That is a narrower, more predictable lever than a kernel extension.
CrashGuard reconciles the disablesleep setting back to a safe state on the next launch, so a crash does not leave the Mac unable to sleep. The enable is always paired with a matching disable on stop, quit, and relaunch.
Changing the pmset disablesleep setting requires administrator authorization. LidRun also shows a heat warning at the same time, because a closed lid traps some heat and you should opt in knowing that.
Closed-lid mode needs the pmset toggle, which is not App Store sandbox-safe. LidRun ships as a notarized, direct DMG instead, so it is still scanned by Apple but can offer a capability the sandbox would forbid.