[FEATURE] Universal session teleporting (local → remote, SSH support)

Resolved 💬 2 comments Opened Dec 19, 2025 by PaulRBerg Closed Dec 19, 2025

Problem

Session teleporting currently only works in one direction: from Claude Code on the web to a local CLI. There's no way to continue a local session on a remote machine (e.g., an AWS instance via SSH).

This limits workflows where you start work locally but need to continue on a more powerful remote machine, or want to hand off a session to a different environment.

Proposed solution

Make --teleport bidirectional and support arbitrary machine-to-machine transfers:

  1. Local → Remote: Export a session from local machine, import on remote (e.g., AWS via SSH)
  2. Remote → Local: Continue a remote session locally
  3. Session export/import: A portable session format that can be transferred via scp, clipboard, or a short-lived sharing URL

Example workflow:

# On local machine
claude --export-session > session.json
scp session.json user@aws-instance:~/

# On remote machine
claude --import-session session.json

Or a more streamlined approach:

# On local machine - generates a one-time code/URL
claude --teleport-out
# Output: Session ready to teleport. Run on target machine:
#         claude --teleport abc123

# On remote machine
claude --teleport abc123

Alternatives considered

  • SSH + tmux: Install Claude Code on remote, use --resume with session ID. Works but requires manual session data sync and doesn't preserve full context.
  • Claude Code on the web: Cloud-native but only supports GitHub repos and doesn't help with private/on-prem environments.

Priority

Medium

Category

CLI commands and flags

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗