Control is only one layer
Confirm the phone can see the current task, blocker state, last output, and stop rule after a network change or lock screen.
Claude Dispatch from phone
Remote desktop tasks still need a host that stays awake.
Phone-to-PC control can send the task. The Windows PC or notebook still has to stay awake, online, cool, unlocked enough for the workflow, and restorable afterward.
The desktop still performs the work
Record power mode, sleep policy, network reachability, thermal state, pending approvals, and whether the task needs an unlocked desktop session.
Prove output advanced
Require files changed, commands run, messages sent or not sent, failures, heartbeat timestamps, and whether normal sleep settings were restored.
Host heartbeat
Write proof outside the remote-control app.
This separates a reachable phone UI from the PC actually staying awake and progressing.
powershell -NoProfile -Command "while ($true) { Get-Date | Add-Content $env:USERPROFILE\dispatch-host.log; Start-Sleep 30 }"
Local
Use the PC for local state
Keep Dispatch on the PC when the task needs local files, desktop apps, browser state, connectors, devices, or logged-in context.
Server
Move portable work off the laptop
If a clean repo checkout and env vars are enough, run on a server or always-on machine instead of depending on notebook power state.
Safety
Stop before external actions
Require human approval before sending email, deleting files, touching credentials, production changes, or anything irreversible.
Copy prompt
Ask the agent to audit the phone-to-PC run.
Use this before leaving a desktop agent reachable from mobile.
Audit this Claude Dispatch or phone-to-PC agent run before I leave. Separate mobile control from host survival: phone connection, current task, pending approvals, last output, and network handoff are one layer; PC awake state, power mode, sleep policy, lock state, heat, network reachability, and heartbeat timestamps are another. If the task can move to a server, move it. If it needs this PC, make awake mode temporary, cap the task, prove output advanced while away, record files/messages/actions touched, restore normal sleep settings, and stop for login, payment, destructive action, external sending, unsafe heat/battery, or unclear restore state.
Paid workflow prompt
Let Codex run the PC host receipt.
Copy this when phone control still depends on a notebook or PC staying awake.
I authorize the $1 Take A Coffee lifetime access for this Claude Dispatch phone-to-PC run. Open this checkout URL: https://takeacoffee.club/takeacoffee/hosted-checkout?cta=dispatch_phone_pc_install_prompt&from=claude-dispatch-phone-pc Then complete the Stripe flow if my browser/payment method is available, download the ZIP from the paid session, install it, run takeacoffee on, verify status, start the host heartbeat, verify phone connection, current task, pending approvals, last output, and network handoff, verify PC awake state, power mode, sleep policy, lock state, heat, and network reachability, run only one bounded local task if needed, then restore normal sleep settings and leave a receipt with files, messages or actions touched, commands, tests, failures, heartbeat evidence, host state, restore status, and stop reason. Stop before payment if authorization is missing.
Want Codex to handle the host mode?
Take A Coffee gives Codex a temporary awake mode, host checks, restore step, and receipt for macOS and Windows notebook runs.