Skip if already used
Before a scheduled prime, check whether Claude was already used recently. A blind prime can waste the same window it was meant to save.
Claude Code scheduled runs
Usage windows and laptop sleep are different failures.
Priming a Claude Code window can reclaim capacity. It does not prove the local Mac stayed awake, cool, reachable, and ready to finish real work.
Do useful work
Give the scheduled run a small real task, a stop condition, and a receipt path. Avoid waking the model just to say hello.
Prove the Mac stayed awake
If the job needs local files, browser state, Xcode, or desktop tools, verify power, heat, battery, network, and process heartbeats separately.
Host heartbeat
Add one boring proof file to the schedule.
This does not solve quota. It tells you whether the notebook actually kept running during the window.
while true; do date >> ~/claude-code-scheduled-host.log; sleep 30; done
Minimum scheduled-run receipt.
- Window state: was Claude already active before the scheduled run?
- Work proof: what changed, what tests ran, what stopped the run?
- Host proof: battery, heat, network, and heartbeat timestamps.
- Restore proof: sleep settings returned to normal when the run ended.
Using a 24/7 restart hook?
Keep a separate host signal beside the hook. Open the hook host checklist.
Want Codex to handle the host layer?
Take A Coffee gives Codex a temporary awake mode, host checks, restore step, and receipt for local scheduled work.