CLAUDE CODE REMOTE WORKFLOW

Let Local Claude Code Control Another Computer Without Public IP

Keep Claude Code and API keys strictly on your laptop—drive remote Macs, headless Linux servers, Windows PCs, Raspberry Pis, and ESP32 boards by 9-digit P2P ID via built-in MCP (rds mcp) and 1-RTT FUSE mount.

Updated 2026-11-21 · RockDesk v1.0.12 · End-to-end encrypted QUIC + TLS 1.3
Key distinction: Anthropic's built-in claude remote-control lets your phone view a Claude Code session already running on one machine. RockDesk solves the opposite problem: keep Claude Code, your login, and API keys strictly on your local laptop, and let that single local Claude Code operate any other Mac, Linux server, Windows PC, Raspberry Pi, or ESP32 behind NAT via a 9-digit P2P ID—without installing Claude on remote machines.

Why Keep Claude Code Local and Treat Remote Machines as Hands?

ApproachClaude Login / API KeysCross-Machine TasksNetwork Requirement
Install Claude on every server + claude remote-controlScattered across every serverIsolated contexts per machineNeeds Claude installed everywhere
VS Code Remote-SSH / SSHFSLocalFragile on Wi-Fi drops, slow small filesNeeds public IP, VPN, or FRP
Local Claude Code + RockDesk (rds mcp)Strictly on your laptopOne session controls N machines9-digit P2P ID, zero open ports

Setup in 3 Steps (60 Seconds)

# Step 1: Install RockDesk on your Mac/PC and on the remote box
brew tap rockdesk-io/tap && brew install --cask rockdesk
# (On headless Linux / Raspberry Pi: curl -fL -o rockdesk.deb https://rockdesk.io/download/latest/linux-amd64 && sudo apt install ./rockdesk.deb && sudo systemctl enable --now rockd)

# Step 2: Authorize your key once (like ssh-copy-id, no passwords afterward)
rds key gen
rds key   # copy this line and run on the remote box: sudo rds authorize "<line>"

# Step 3: Wire RockDesk into Claude Code (choose MCP or Skill — or both)
claude mcp add -s user rockdesk -- rds mcp
npx skills add rockdesk-io/rockdesk-skill

What You Can Ask Claude Code Immediately

Security Model

Every connection is end-to-end encrypted with QUIC + TLS 1.3; relay servers only forward ciphertext. The remote machine decides who can connect (prompt to allow, one-time password, fixed password, or rds authorize key pair) and can toggle individual features (terminal, files, mount, screen, port forwarding) on or off independently.

Frequently asked questions

How is RockDesk different from Anthropic's claude remote-control?

claude remote-control lets you view and steer a Claude Code session that is already installed and running on one computer from your phone or browser. RockDesk lets a single local Claude Code on your laptop control multiple remote computers (Mac, Linux, Windows, Raspberry Pi, ESP32) without installing Claude or storing API keys on those remote machines.

How do I add RockDesk as an MCP server in Claude Code?

After installing the RockDesk app (which includes the rds CLI), run claude mcp add -s user rockdesk -- rds mcp. You can also install the companion skill with npx skills add rockdesk-io/rockdesk-skill.

Does the remote Linux server need a desktop GUI or public IP?

No. Install the RockDesk .deb (x86_64 or arm64), enable sudo systemctl enable --now rockd, and check its 9-digit ID with sudo rds status. No display server, SSH port, or public IP is needed.

What happens if my laptop switches Wi-Fi or disconnects during a long command?

Remote rds shell sessions stay alive on the target machine for 30 minutes by default after disconnect (re-attachable with --attach), and long background jobs can run via spawn.

Try RockDesk free for 10 days per device

Windows, macOS (Apple silicon & Intel), Linux (x86_64 & arm64), Android & ESP32. Install on macOS via brew tap rockdesk-io/tap && brew install --cask rockdesk.

Download RockDeskSkill & MCP Docs