Intermediate8 min
Remote Sessions and Cross-Device Workflows
Remote Control, Teleport, and --remote give you three distinct ways to work across devices and locations. Understanding which is which — and what each one preserves — makes cross-device Claude Code workflows practical.
Quick Reference
- →Remote Control (Feb 2026): monitor a local session from mobile/web — session stays on your machine
- →Teleport: pull a cloud session (started on web/mobile) down to your local terminal
- →--remote: run a session on Anthropic's cloud infrastructure — continues when you disconnect
- →/rc or /remote-control: enable Remote Control for an existing session mid-conversation
- →Session URLs and QR codes: quick access from phone
- →Push notifications: alert you when Claude needs input or finishes a task (v2.1.110+)
Three Cross-Device Modes
There are three distinct ways to work with Claude Code across devices and locations. They are often confused with each other — understanding the difference is the key to using the right one.
| Mode | Session runs on | You access from | Session survives disconnect? |
|---|---|---|---|
| Remote Control | Your local machine | Mobile, web, or another terminal | Yes — session stays on your machine |
| --remote (cloud) | Anthropic's infrastructure | Any device via URL | Yes — cloud-hosted |
| --teleport | Pulled to local machine | Local terminal (target) | No — it's now local |
Remote Control is the most common pattern
For most cross-device workflows, Remote Control is what you want. You start a session on your workstation, close the laptop, and continue from your phone or tablet. The session — including MCP servers, filesystem access, env vars — stays on the original machine.