Time limit
Pick a session length so your Mac does not stay awake forever.
SleepWalk keeps your Mac awake for long Cursor, Claude Code, Codex, Windsurf, and terminal-agent runs, then lets the session end when the agent signals done.
SleepWalk keeps the Mac awake underneath your editor, CLI, or coding assistant.
The SleepWalk skill gives AI coding agents a local done signal. When checks pass, the agent stops the timer itself.
> Fix the flaky upload queue test while I step away.
• I’ll use the SleepWalk skill to keep a bounded session open, then stop it when checks pass.
• Explored
└ Read SKILL.md (SleepWalk skill) • Ran sleepwalkctl start
└ Session active … fixed retry timing and reran the focused suite …
• Ran npm test -- UploadQueue
└ 18 passed … task complete, sending SleepWalk the done signal …
• Ran sleepwalkctl done
└ Agent marked done
Session inactive • Done. SleepWalk timer stopped.
Agent agnostic. No prompt monitoring. No window watching. Just a local done signal.
Set the boundaries before you walk away: how long, how much battery, and what temperature level is acceptable.
Pick a session length so your Mac does not stay awake forever.
Choose the lowest charge you are comfortable reaching.
Stop automatically before temperature becomes a problem.
SleepWalk is for software engineers who leave AI coding agents running in Cursor, Claude Code, Codex, Windsurf, terminals, and local dev tools, then need to step away or close the lid.
Yes. SleepWalk is designed for closed-lid agent runs when macOS and your hardware setup allow them. Start a bounded session, close the lid, and let the agent continue while SleepWalk watches your limits.
Those tools can keep a Mac awake, but they are easy to leave running. SleepWalk is built for AI-agent work: quick menu setup, explicit battery and temperature guardrails, closed-lid sessions, and agent auto-stop through the SleepWalk skill.
Yes. Install the SleepWalk skill once, and an AI coding agent can start a session, mark itself active or idle, and stop the timer when the task is done.
SleepWalk is agent-agnostic. Any coding assistant, editor, CLI, script, or workflow that can call the local SleepWalk CLI can use the same bounded session controls.
No. SleepWalk does not inspect prompts, windows, logs, code, or network traffic. Agent auto-stop uses explicit local signals from the SleepWalk skill and CLI.
SleepWalk ends the session when the timer expires, the battery drops below your floor, the Mac gets too hot, or the agent marks the task done.
SleepWalk pricing is shown at checkout.