Workers need proof
Do not trust a queue length or tmux pane alone. Check timestamps, output files, worker logs, and whether the actual job advanced while the lid was closed.
MCP, local models, harnesses
Local agent stacks need a host contract.
Routers, MCP servers, browser profiles, local model workers, and file watchers all assume the notebook keeps running.
Budgets need caps
Long local runs need battery, thermal, disk, memory, network, and token budgets before they are left unattended.
Modes need exits
Temporary awake settings should have a clear off path, a receipt, and a baseline check so the next operator is not inheriting mystery state.
Host heartbeat
Prove the machine kept serving the stack.
Run this next to an MCP server, local model worker, or browser harness and verify the timestamps continue through the closed-lid window.
while true; do date >> ~/local-agent-stack-host.log; sleep 15; done
What to require before a long local run.
- Temporary awake mode only when the stack needs this notebook.
- Battery and heat checks before closed-lid or transport work.
- Heartbeat evidence from the host and from the worker process.
- Restore normal sleep settings and leave a receipt with process state, files changed, failures, and next decision.
- caffeinate vs closed-lid MacBook checklist
Want Codex to handle the host mode?
Take A Coffee gives Codex a temporary awake mode, host checks, restore step, and receipt for local macOS and Windows agent stacks.