Keep a Claude Code session running on a remote box and steer it from your phone

Claude Code's docs say: "If you run claude from a terminal on a remote machine, start it inside tmux or screen to keep the session running after you disconnect from SSH." One command attaches or creates the session, so you can rerun it after every drop: ssh devbox -t tmux new-session -A -s agents.

One developer's daily setup: "ghosty + ssh + mosh + tmux + claude code (sometimes codex)." He is honest about what still hurts: copy-paste works about 95% of the time, and pasting or dragging images and videos into the remote session does not work well. The tmux guide's advice: pair tmux with mosh "if your link is bad enough that SSH itself keeps dying."

In the project directory on the server, run claude remote-control (server mode, which shows a URL and, on spacebar, a QR code). Or inside a running session, type /remote-control to carry the current conversation over. Then open the session at claude.ai/code or in the Claude app under Code. Requirements from the docs: a Pro, Max, Team or Enterprise plan with claude.ai sign-in; "API keys are not supported"; it does not work through Bedrock, Agent Platform, Foundry or a non-Anthropic ANTHROPIC_BASE_URL. On Team and Enterprise an Owner must enable it first.

A developer who drives Claude Code on servers from Desktop, mobile and web: "The massive upside is that the actual work happens on the server so you can close your laptop and it will continue." The cost: "every new project requires a setup step on the server (to add the systemd service) where you will develop it since Claude can only handle one server per directory." He did not share the unit file, so this guide does not either.

With Remote Control active, run /config and enable "Push when actions required" for permission prompts and questions, "Push when Claude decides" for finished tasks, or both. If you will open several sessions from your phone, start the server with --spawn worktree so "each on-demand session gets its own git worktree." If you stop the server, claude remote-control --continue brings the session back for about four hours.

One developer hands tmux sessions to Claude but keeps logins in his own hands: "Paranoid me uses the macbooks secure enclave with fingerprint for the ssh key so claude can't ssh into my remote boxes by himself. I then open named tmux sessions, perform the ssh login via fingerprint, and then tell claude that he is free to take over that session with a given name."