Local agents and CLI tools still exist
Many developers run terminal agents, Cursor, VS Code, Aider, OpenCode, npm, Python, Rust and custom scripts directly on their machine. If the machine sleeps, the work can stop.
Local AI Agent Sleep Guard for developers
Your local AI agents die when your laptop sleeps. Stop losing work.
Cloud agents are useful. But local agents and CLI workflows still exist. Developers still use terminal tasks, Cursor, VS Code, Docker, local dev servers, Flutter/Gradle, npm, Python, Rust, databases and emulators. If your laptop sleeps, all of that can stop.
Local AI agentsCursor & VS CodeTerminal CLI tasksDocker & dev serversFlutter / Gradle / npmPython / Rust / databases
The local workflow problem is not gone
Cloud coding did not eliminate your local machine.
The new wave of cloud coding is useful, but real developers still run serious work locally. Cursor, VS Code, terminal CLI agents, Docker containers, local dev servers, Flutter/Gradle builds, npm scripts, Python jobs, Rust builds, databases and emulators can all stop when a laptop sleeps.
Your dev stack is not only in the cloud
Docker, local databases, emulators, local dev servers, test runners, Flutter/Gradle builds and package scripts often depend on an awake laptop.
Closed lid should not kill progress
CloseLid is being built as a controlled closed-lid developer workflow guard: protect local work, watch safety conditions, and stop when protection is no longer needed.
Features
Built for the local work cloud agents do not replace
CloseLid focuses on high-intent developer workflows: local AI agents, CLI tasks, Docker, local dev servers, builds, databases and emulators that can stop when a laptop sleeps.
Local AI Agent Guard
Keep local AI agents and AI coding workflows running when the laptop lid closes and normal sleep would interrupt them.
CLI & Terminal Protection
Built for terminal CLI agents, long shell commands, npm scripts, Python background tasks, Rust builds and custom automation.
Cursor & VS Code Workflows
Designed for developers who use Cursor, VS Code terminals and local AI-assisted editing, refactoring and test-repair sessions.
Docker, Databases & Dev Servers
Protect Docker containers, local databases, emulators and local dev servers from being interrupted by laptop sleep.
Flutter / Gradle / npm Builds
Long builds and package scripts should not die because the laptop lid closed during an AI-assisted workflow.
Safety-Aware Closed-Lid Mode
Battery-aware, thermal-aware and auto-off principles keep CloseLid positioned as controlled protection, not reckless sleep bypassing.
Auto-Off When Tasks Finish
The goal is not to keep your laptop awake forever. The goal is to protect real work, then safely give control back.
Mac First, Windows Planned
CloseLid starts with macOS closed-lid developer workflows, with Windows support planned after demand is validated.
Fast, Focused, Not Bloat
A small developer utility should be lightweight, predictable and easy to trust — not another heavy background app.
Supported local workflows
For Cursor, VS Code, terminal CLI agents, Docker and real local dev stacks
CloseLid is not only about one cloud tool. It is for the developer work that still runs on your machine and still stops when your laptop sleeps.
Cursor & VS Code
Keep local AI edits, integrated terminals, refactors, test repairs and dev server workflows alive while you step away.
Terminal CLI agents
Protect Aider, OpenCode, Codex-style CLI sessions, long-running shell tasks and local automation from laptop sleep.
Docker & local dev servers
Avoid interrupted containers, stopped Node/Vite/Next dev servers, broken API mocks and local service crashes.
Flutter, Gradle, npm
Keep mobile builds, Android Gradle tasks, package scripts, bundlers and test runners alive during closed-lid workflows.
Python, Rust & background jobs
Long Python scripts, Rust builds, cargo tasks and background workers should not disappear because the machine slept.
Databases & emulators
Local PostgreSQL, SQLite workflows, Redis, Android emulators and development databases can depend on an awake laptop.
How it works
A controlled path from local work to closed-lid continuity
Start the local workflow, enable protection deliberately, close the lid with safeguards, then return without discovering a dead terminal or broken build.
Start local work
Kick off Cursor, VS Code, a terminal CLI agent, Docker, a dev server, a Flutter/Gradle build, npm script, Python job, Rust build, database or emulator.
Enable CloseLid intentionally
Use a deliberate guard mode built for local AI coding workflows, not a blind always-on hack.
Close the laptop with safeguards
Closed-lid protection should respect battery, thermals, power state and responsible operating limits.
Return without losing the session
Come back to a cleaner workflow with fewer broken runs, fewer dead terminals and less manual babysitting.
Safety-first closed-lid control
Not reckless sleep bypassing. Controlled protection for local developer work.
CloseLid is positioned around responsible closed-lid workflows: power checks, battery limits, thermal awareness, manual activation and auto-stop logic. It is for protecting real local work, not for throwing a running laptop into a bag.
Battery-aware protection
Thermal-aware checks
Power-adapter-first workflow
Manual, controlled activation
Auto-off when local tasks finish
Early access
Need local AI agents to keep running with the lid closed?
Tell us what you use: Cursor, VS Code, terminal agents, Docker, local dev servers, Flutter/Gradle, npm, Python, Rust, databases or emulators. Early users will shape the CloseLid beta.
support@closelid.comRequest Early AccessNo backend form is connected yet. This opens your email app and sends the request to support@closelid.com.
FAQ
Questions before your local workflow sleeps
CloseLid is being shaped around the developer workflows that still happen locally and still need controlled protection.
Is CloseLid still useful if cloud coding agents exist?
Yes. Cloud agents are useful, but local AI agents and local developer workflows still exist. Cursor, VS Code, terminal CLI agents, Docker, local dev servers, builds, databases and emulators can still stop when your laptop sleeps.
What local workflows is CloseLid for?
CloseLid is for local AI agents, terminal tasks, Cursor, VS Code, Docker, local dev servers, Flutter/Gradle, npm scripts, Python jobs, Rust builds, local databases and emulators.
Is CloseLid just a normal keep-awake app?
No. The positioning is a safety-aware closed-lid developer workflow guard, focused on AI coding agents and local dev tasks rather than generic always-awake behavior.
Is it safe to close a laptop while work continues?
It must be controlled. CloseLid is planned around battery-aware and thermal-aware protections, manual activation and auto-off logic. It should not be used recklessly or inside a bag.
Does it support macOS and Windows?
The planned path is macOS first, with Windows support after demand is validated.
Who should join early access?
Developers whose local AI, CLI, Docker, build, emulator or database workflows stop when the laptop sleeps should request early access.