ArthurZakirov Manage Caffeinate
Overview
Use this skill to manage a machine-level macOS caffeinate job. This is not Codex-specific; it keeps the Mac awake for any local terminal, Codex, Claude Code, browser, or agent process that depends on the machine staying awake.
The preferred mechanism is a launchd-managed job named agentdesk-caffeinate, which runs:
/usr/bin/caffeinate -dimsu
Workflow
Run the bundled script from the installed skill:
bash "$HOME/.codex/skills/manage-caffeinate/scripts/manage-caffeinate.sh" status
bash "$HOME/.codex/skills/manage-caffeinate/scripts/manage-caffeinate.sh" on
bash "$HOME/.codex/skills/manage-caffeinate/scripts/manage-caffeinate.sh" off
If the skill is being run from a cloned AgentDesk checkout instead of an installed Codex skill, run:
bash "skills/manage-caffeinate/scripts/manage-caffeinate.sh" status
Commands
on: create or refresh the launchd job. Also removes the legacycodex-caffeinatelabel if present.off: remove the launchd job and clean up matching managed/usr/bin/caffeinate -dimsuprocesses.status: show launchd status andpmset -g assertionscaffeinate lines.restart: remove and recreate the launchd job.
Verification
After turning it on, verify pmset -g assertions lists /usr/bin/caffeinate or a caffeinate command-line tool assertion with PreventUserIdleSystemSleep, PreventUserIdleDisplaySleep, and PreventSystemSleep.
After turning it off, verify launchctl list agentdesk-caffeinate fails and pmset -g assertions no longer lists the caffeinate assertions.
Reference
Read references/setup.md when you need to explain how the launchd setup works, why launchd is used instead of a background shell process, or what was initially configured on Arthur's machine.
Boundaries
caffeinate prevents idle sleep while macOS allows the assertion. Closing a MacBook lid can still force sleep unless the machine is in a supported clamshell setup, typically connected to power and external display/input.