Completion is not supervision
Keep the goal concrete: acceptance test, changed-file boundary, stop rule, time cap, and a review gate before external side effects.
Claude Code /goal mode
Claude can keep pursuing a completion condition across turns. The separate risk is local: sleep, lid state, battery, heat, Wi-Fi, and restore.
Keep the goal concrete: acceptance test, changed-file boundary, stop rule, time cap, and a review gate before external side effects.
Use a heartbeat file and system logs so you can tell whether the Mac kept working or woke later with the session intact.
If temporary awake mode was needed, the run is not finished until battery/heat are checked and normal sleep settings are restored.
Host heartbeat
Start this beside the local goal run, close or lock the notebook for a short test window, then check whether timestamps kept moving.
while true; do date >> ~/claude-code-goal-host.log; sleep 30; done
Use this before a local run that may continue while you are away from the notebook.
Before starting this Claude Code goal, create a host receipt plan. State the completion condition, allowed files, tests, time cap, retry cap, and stop rules. Separately verify the local host: battery, heat, network reachability, sleep/wake logs, and an external heartbeat file. If the run needs closed-lid or unattended time, make awake mode temporary and restore normal sleep settings at the end. Stop for payment, login, destructive ambiguity, or unsafe heat/battery state.
Take A Coffee gives Codex a temporary awake mode, host checks, restore step, and receipt for local goal runs on macOS and Windows.