An Overwatch session lives in the cloud, not on the machine that started it. Open it on your Mac, steer it from your phone, close the lid, come back. It is the same session, still running, still yours.
“Currently, sessions are tied to the terminal/machine they started on.”
GitHub #47926 · anthropics/claude-code, closed as duplicate. Filed again as #52052.
View the source ›
This is the thing Overwatch was built for. Sessions live in the Mainframe, so the same messages stream live on phone, desktop and tablet at once, with real handoff. No Max-tier gate, no single-controller limit. Anthropic shipped Remote Control in Feb 2026, but it is a Max-only research preview with one controller. Ours is open to every account.
Not a copy, not a sync-on-close. The same token stream paints on your desktop, your tablet and your phone at the same moment.
The session keeps its place: model, intensity, queue, open files, scrollback. Reopen it anywhere and it picks up mid-sentence.
Live tool calls, file writes and shell output stream as they happen, so a run that stalls is visible in seconds instead of discovered an hour later.
You start a refactor at your desk, walk to a meeting, and open your phone. The session is already there, mid-run, still streaming. You type one correction and put the phone away. Fifteen seconds, no reconnect, no re-explaining. That is the exact scenario in the closed GitHub thread, shipped.
One session in the Mainframe. Every device is a window onto it, not a copy of it.
Per-session model, intensity, directives and queue all live with the session, not in a local dotfile. Reinstall, switch laptops, or grab someone else's machine: the session is unchanged.
All of it lives with the session, not in a local dotfile.