Skip to content
Datfx Labs Claude Guide

Teleport: Session Mobility

Claude Code sessions are not tied to a single machine. claude --teleport pulls a cloud session down to your local terminal. /remote-control pushes commands from a remote device into a local Claude Code session. Together they let you start work anywhere and continue it everywhere.

The Two Commands

claude --teleport

Moves a running cloud session to your local machine. The session state — conversation history, file context, tool results, in-progress task — transfers to your terminal. The cloud session ends.

Terminal window
# On your local machine — pull down an active cloud session
claude --teleport <session-id>


# Or let Claude Code find active sessions automatically
claude --teleport
# → Lists active cloud sessions, select one to pull down

/remote-control

Pushes a command from a remote device (phone, tablet, another machine) into a local Claude Code session that is already running. The local session executes the command as if you typed it there.

Terminal window
# On your remote device — push a command to your local session
claude remote-control --session <session-id> --send "pause and wait for me"
claude remote-control --session <session-id> --send "run the tests now"


# On your local machine — enable remote control for your session
/remote-control --enable
# → Outputs a session-id and access token for remote commands

Session Mobility Flow

flowchart LR PHONE["Mobile / Remote\nDevice"] CLOUD["Cloud Session\n(claude.ai)"] LAPTOP["Local Terminal\n(laptop)"] PHONE -- "start task on claude.ai" --> CLOUD CLOUD -- "claude --teleport\n(pull state down)" --> LAPTOP LAPTOP -- "continue seamlessly" --> LAPTOP PHONE2["Mobile / Remote\nDevice"] LOCAL2["Local Session\n(running)"] PHONE2 -- "/remote-control\n--send 'command'" --> LOCAL2 LOCAL2 -- "executes command\nremotely" --> LOCAL2 style PHONE fill:#1e293b,color:#7dd3fc,stroke:#334155 style CLOUD fill:#1e293b,color:#7dd3fc,stroke:#334155 style LAPTOP fill:#1e293b,color:#86efac,stroke:#334155 style PHONE2 fill:#1e293b,color:#7dd3fc,stroke:#334155 style LOCAL2 fill:#1e293b,color:#86efac,stroke:#334155

Use Case: Start on Mobile, Continue Locally

The most common scenario: you are away from your desk, start a task on claude.ai from your phone, then return to your laptop and want to pick up exactly where you left off — in your terminal, with full tool access.

Step 1 — On your phone (claude.ai):

Start a task in the web interface. Claude begins working. The session accumulates context: files read, decisions made, code written.

Step 2 — At your laptop:

Terminal window
# Teleport the cloud session to your local terminal
claude --teleport


# Claude Code lists active sessions:
# → session-abc123  [2 hours ago]  "refactor auth module"  (in progress)
# Select: session-abc123

Step 3 — Seamless continuation:

Your terminal now has the full session state. Claude continues the task with complete awareness of everything that happened in the cloud session. Files Claude referenced are available locally. The task picks up mid-step if it was in progress.

Setup Requirements

For claude --teleport

  • Claude.ai Pro account (cloud sessions require Pro)
  • Active cloud session (started via claude.ai web or mobile app)
  • Local Claude Code installed and authenticated: claude auth status
  • Both devices authenticated with the same Claude.ai account

For /remote-control

  • Local Claude Code session must be running and have remote control enabled
  • Remote device must have Claude Code CLI installed, or use the claude.ai mobile app’s remote control feature
  • Both devices authenticated with the same account
  • The session ID and access token from /remote-control --enable
Terminal window
# Enable remote control on your local session
/remote-control --enable


# Output:
# Remote control enabled
# Session ID: session-xyz789
# Access token: rc_tok_xxxxxxxx
# Use: claude remote-control --session session-xyz789 --token rc_tok_xxxxxxxx --send "command"

Store the access token securely — it grants control of your local Claude Code session.

Example: Full Mobile-to-Desktop Workflow

8:00 AM — On the train, phone:

Open claude.ai, start a task:

“Review the authentication module in the datfx/api repo. Identify the top 3 security issues and propose fixes for each.”

Claude begins reading the repo, analyzing the auth module, building context.

9:00 AM — At your desk, laptop:

Terminal window
claude --teleport
# → Selects the "auth module review" session


# Your terminal shows the session is mid-analysis.
# Claude continues:
# "I've identified the three issues. Now generating the fix proposals..."

Claude continues seamlessly. You have full terminal access — you can read files, run tests, apply patches — all with the context Claude built on your phone.

Later — Need to step out briefly:

Enable remote control so you can nudge the session from your phone:

Terminal window
/remote-control --enable
# → session-xyz789, rc_tok_xxxxxxxx

From your phone, push a command:

Terminal window
claude remote-control --session session-xyz789 --token rc_tok_xxxxxxxx \
  --send "pause on the third fix and wait for my review"

Your local Claude Code session receives the command and pauses, waiting for you to return.

Gotchas

Active session required for teleport. You cannot teleport a completed or expired session. If the cloud session timed out, the state is gone. Teleport must happen while the session is still active.

Latency on large sessions. Transferring a session with extensive context (many files read, long conversation) takes a few seconds. Very large sessions (near context limit) may take 10–15 seconds to transfer.

Local files must exist. If Claude referenced a file path during the cloud session that does not exist on your local machine (e.g., a file only on the cloud environment), teleporting will succeed but Claude will need to re-read or re-create those files locally.

Remote control security. The access token grants real execution authority over your local Claude Code session. Treat it like a password. Revoke it when done:

Terminal window
/remote-control --disable

One active session per teleport. You can only teleport one session at a time. If you have multiple active cloud sessions, claude --teleport lists them and you select one.