Origin story

It started with one half-open laptop.

A meme about software engineers before and after coding agents captured a real shift: the laptop is no longer just a screen. It is the place where long-running local agents, builds, tests, and remote sessions keep working after you walk away.

See the agent workflow Back to overview
Meme screenshot titled software engineers before vs after agents, showing a laptop fully closed before agents and partly open after agents.
The meme that made the problem obvious: agents keep working after the screen stops being the point.

What changed

Before agents, closing the lid was normal. After agents, it became an interruption.

The joke

Agents made one old laptop rule feel newly wrong.

The meme landed because it was true: once an agent is running, closing the laptop is no longer the end of the work. The machine still has the repo, credentials, terminal sessions, local servers, and context.

The first need

Keep the local harness alive while stepping away.

Claude Code, Codex, builds, tests, downloads, and remote terminals all want the same boring guarantee: the Mac should stay awake when the lid closes, without disabling sleep forever.

The product shape

A tiny native utility, not a new workflow platform.

OpenLid became a menu bar app and CLI around one job: prevent sleep precisely, show the state clearly, and get out of the way. Remote access stays yours; OpenLid keeps the laptop side alive.

The guardrails

Useful on the go, careful with the machine.

Schedules, battery thresholds, transit safeguards, signed releases, and zero telemetry turned the idea from a quick workaround into a utility people could leave running with confidence.

How it developed

The useful version stayed small.

The tempting answer would have been a bigger remote-coding system. The better answer was narrower: make the Mac reliable as the machine running the work, then let developers keep using the remote tools they already trust.

That shaped OpenLid into a native menu bar app with a first-class CLI. One click or one command can arm sleep prevention; schedules keep it scoped to working hours; safeguards turn it off when the battery or travel context says the laptop should sleep.

The result is deliberately boring infrastructure for an increasingly normal habit: start a local coding harness, close the laptop, and check in later from a phone without killing the session.

the original shape

// keep the idea smaller than the meme

$openlid on

✓Active — preventing sleep now

$tmux new -s codex

$codex

Local agent running on the laptop

// phone reconnects later; Mac stays awake

OpenLid exists for that half-open moment.

The lid can close. The screen can stop being useful. The work can keep running on the laptop that already has everything it needs.

Download OpenLid