Launching today
LidRun
Keep AI working on your Mac — even with the lid closed
28 followers
Keep AI working on your Mac — even with the lid closed
28 followers
A safety-aware Mac runtime for Claude Code, Cursor, Codex, Docker, Ollama and local LLMs — with closed-lid workflows, timers, charging-only mode, low-battery auto-stop and thermal guardrails. Built for developers who need to keep AI/dev jobs running on Mac, keep a Mac awake with the lid closed, or use a more guided alternative to blind wake locks like caffeinate.
Hey 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?
Does the thermal guardrail actually throttle the underlying job or just kill it outright when temps cross a threshold?
@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.
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.
@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
I’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.
@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.
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.