Get the weekly radar
One short email with the freshest products, every week.
LidRun keeps a MacBook awake with the lid closed for AI agents and dev processes.
Grounded in available product and source data
Keep your Mac awake, lid closed, for AI agents is exactly the gap LidRun fills — closing a MacBook lid normally suspends everything, which is a real problem for a long-running Claude Code session or Docker build that still has work left to do.
Auto Mode is the specific feature built for that use case: it detects Claude Code, Cursor, Docker, and Ollama directly, and recognizes an active agent even at 0% CPU usage so a session doesn't get killed mid-task just because it's momentarily idle. Once the actual work finishes, custom command execution can auto-release the session automatically, rather than requiring someone to remember to open the lid back up.
What keeps this from being a reckless battery-drain risk is a real set of guardrails: session timers cap a run between 30 minutes and 8 hours, a charging-only mode restricts closed-lid operation to when the Mac is plugged in, low-battery auto-sleep kicks in around 4-5% to prevent data loss, and thermal monitoring backs off automatically if the Mac starts running hot. Real-time session status shows exactly why the Mac is currently awake and when the session is set to release, so nothing runs as a mystery background process.
The site positions this specifically against two familiar alternatives: caffeinate, built for simple sessions rather than guarded AI/dev workflows, and Amphetamine, described as general-purpose automation without the same workload-aware safety checks. Pricing runs three one-time-payment tiers rather than a subscription — a permanent Free tier covers simple lid-open sessions with the core safety features, Pro adds Closed-Lid Mode and Auto Mode scaled by number of Macs, and a Startup tier covers 10 Macs for teams of 5 or more. One limitation worth noting directly: LidRun is macOS-exclusive and not available on the Mac App Store, so it has to be installed outside the usual App Store flow.
Yes — Auto Mode specifically recognizes an active agent even at 0% CPU usage, which prevents a session from getting cut off mid-task just because it's momentarily not using processing power.
The session ends itself rather than draining fully — auto-sleep is designed to kick in before the battery bottoms out, prioritizing not losing unsaved work over finishing the run.
Not by default if it's configured for auto-release — the point of that setting is exactly to avoid a Mac sitting awake unnecessarily after the actual task no longer needs it.
The site frames caffeinate as built for simple sessions, while LidRun adds workload-aware detection, safety guardrails, and runtime-based auto-release specifically for AI agents and dev processes rather than just preventing sleep indefinitely.
No, per the FAQ — it's not available there, so installation happens outside the usual App Store flow, with Apple notarization addressing the security warnings that would otherwise show up on first launch.
These 8 comments were collected from the discovery source. ProductVisit does not host replies in Release A.
love that lidrun gives per-app controls instead of just blanket caffeinate flags, and the low-battery auto-stop is the kind of thing that should've shipped with macOS years ago. really thoughtful execution here.
1 source upvotesI’ve also used the pmset command, and it either shut the Mac down midway or kept it running until the system became overloaded. Lidrun might be a better and safer option. The initial experience is quite impressive; however, I’ll come back to give a more detailed review once I’ve had more experience with it.
1 source upvotesDoes the thermal guardrail actually throttle the underlying job or just kill it outright when temps cross a threshold?
1 source upvotes@sarah_hanah Thanks Sarah — I’ve been there too. :)) pmset is powerful, but it’s easy to leave the Mac in a state you didn’t intend, especially for long or overnight runs. That’s why I wanted LidRun to feel more guided and safety-aware: timers, charging-only mode, low-battery auto-stop, thermal awareness, and release when conditions are no longer good. Would love to hear your feedback after you’ve used it more.
1 source upvotesHey Product Hunt 👋 I’m Henry, maker of LidRun. I built LidRun because AI coding tools exposed an old Mac problem in a new way. Claude Code, Codex, Cursor, Docker, Ollama,... and long-running terminal jobs can keep working long after you step away. But macOS still thinks in old idle/sleep patterns. Close the lid, walk away, or leave a long run overnight — and the work may stop at the worst time. The usual fixes are caffeinate, Amphetamine, or pmset. They are useful, and I respect them. But for daily AI/dev workflows, I wanted something more explicit: Keep work running when it is still active Support closed-lid workflows carefully Stop on low battery or safety limits Avoid leaving a blind wake lock on forever Show why the Mac is being kept awake That is the idea behind LidRun: Agent running → stay awake. Agent done or unsafe → release. LidRun is free to start. The core safe workflow is free forever, and Pro is one-time with no subscription. I’m especially looking for feedback from Mac developers using Claude Code, Cursor, Docker, Ollama, local LLMs, or long-running terminal jobs. What should LidRun watch for next?
Small thank-you for the Product Hunt community: Click LifeTime on this page, copy the code, then claim lifetime Pro here: https://lidrun.com/redeem Would love feedback from Mac developers running Claude Code, Cursor, Docker, Ollama or long AI/dev tasks.
@dursunipfi Thanks Dursun — you got exactly what I’m trying to solve. A blanket wake lock is useful, but it is easy to forget it is still on. LidRun is built more around the workflow: what is actually running, whether the Mac should still stay awake, and when it should stop because battery or safety conditions are no longer good. Low-battery auto-stop was one of the first guardrails I wanted in the product. <3
@umuthwfs Great question. LidRun does not throttle or kill the underlying job by default. It manages the LidRun runtime session — if conditions are no longer good, it releases the wake/closed-lid hold so macOS can manage sleep normally again. For example, on very low battery, LidRun can let the Mac sleep around 4% instead of forcing it to keep running until a hard shutdown or restart. The goal is to protect the machine and reduce the chance of losing unsaved work or runtime data. So LidRun is not secretly killing Claude, Codex or Cursor. It is stopping the “stay awake” layer when safety conditions are no longer good.