Phone access handles prompts
Use the phone or remote terminal to answer blockers, inspect output, and approve the next bounded step. Keep that layer independent from host power state.
Claude Code on the go
Remote control is not the same as a reliable local host.
Phone terminals, SSH, Tailscale, tmux, and notifications help you steer Claude Code away from the desk. The notebook still has to stay awake, reachable, cool, and restorable.
The notebook still does the work
If Claude needs local files, browser state, desktop apps, simulators, or running services, test battery, heat, network, and sleep/wake before leaving.
Know what happened while away
Require timestamps, files changed, commands run, tests, failures, stop reason, and whether normal sleep behavior was restored.
Host heartbeat
Leave a proof file outside the terminal session.
This separates a reachable phone UI from the local notebook actually staying alive.
while true; do date >> ~/claude-code-on-the-go-host.log; sleep 30; done
Copy prompt
Ask the agent to split remote control from host survival.
Paste this before leaving Claude Code reachable from a phone or remote terminal.
Audit this Claude Code on-the-go setup before I leave the desk. Separate remote control from host survival: phone/SSH/Tailscale/tmux access, pending approvals, cwd, and output state are one layer; local notebook awake state, battery, heat, Wi-Fi, and heartbeat timestamps are another. If the task can run on a server, move it there. If it needs this notebook, make awake mode temporary, cap the task, leave a receipt, and restore normal sleep settings. Stop for login, payment, destructive ambiguity, unsafe heat/battery, or unclear restore state.
Want Codex to handle the local host layer?
Take A Coffee gives Codex a temporary awake mode, host checks, restore step, and receipt for macOS and Windows notebook runs.