Move Sessions Between Devices

Remote workflows are useful when a Claude Code task outlives the device you started on.

We already recommend Remote Control for monitoring long-running laptop sessions from your phone. Device handoff extends that idea: keep the work moving when you switch between laptop, phone, and cloud sessions.

Useful commands

• /remote-control: control or monitor a running local session remotely.
• /teleport: move a cloud session down to your laptop when you need local control.

Good uses

• Start a cloud task from your phone.
• Continue a cloud session locally when you return to your laptop.
• Monitor a laptop session while away.
• Respond to approvals or questions without sitting at the terminal.

Practical advice

Use descriptive session names before handoff. It is much easier to resume or move work later when the session name matches the task.

Troubleshooting

If /remote-control is missing or reports that it is unavailable, check your privacy settings before anything else. Remote Control sits behind a feature flag, so Claude Code has to reach Anthropic’s feature-flag service to learn that your account is eligible. Variables that block non-essential traffic can block that check too, which leaves the cached flags stale and the command hidden.

Check both variables:

echo $DISABLE_TELEMETRY
echo $CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC

An empty result does not clear them. These are often set under env in ~/.claude/settings.json, where a shell check shows nothing while Claude Code still applies them. Look in both places.

If either is set, delete the line. Do not set it to "0". Claude Code checks whether these variables are present, not what they contain, so "0" still counts as set and still blocks the traffic. DISABLE_TELEMETRY: "0" behaves exactly like "1".

Then:

• Start a new session so the flags are fetched fresh.
• Run claude doctor to see which eligibility check is failing.
• Clear Claude Code’s feature-flag cache if the command is still missing. Stale evaluations can outlive the setting that froze them.

One documented cause is unrelated to telemetry: ANTHROPIC_BASE_URL disables Remote Control when it points anywhere other than api.anthropic.com, including an LLM gateway or proxy. Unset it and restart.

This is the tradeoff behind our telemetry settings. DISABLE_TELEMETRY is a reasonable default right up until you want Remote Control, and then it is the first thing to check.