# Use Claude Code from your phone with Remote Control > How Claude Code's Remote Control lets you continue a session running on a remote machine from the Claude app, what it needs, and how shedix sets it up. *2026-10-24 ยท claude-code, phone, codex* Remote Control connects the Claude app on your phone, or claude.ai/code in any browser, to a Claude Code session running on a computer. The session stays on that computer: commands run there, and files are read and written there. Your phone becomes a window into it. You read along, answer questions, approve actions and send the next instruction. That design has one consequence that matters more than any setting. The computer has to stay on, and the `claude` process has to keep running. On a laptop in your bag, neither is true for long. On a machine in the cloud, both are the normal state. ## What it needs From [Anthropic's Remote Control docs](https://code.claude.com/docs/en/remote-control): - **A claude.ai plan:** Pro, Max, Ultra, Team or Enterprise. API keys aren't supported, and on Team and Enterprise an Owner has to turn Remote Control on first. - **A claude.ai sign-in on the machine:** log in with `claude auth login` or `/login`. A long-lived token from `claude setup-token` can't start Remote Control, because it can only make model requests. - **The Anthropic API directly:** it isn't available through Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry, or an `ANTHROPIC_BASE_URL` that points somewhere else. - **A trusted folder:** Claude Code asks once whether to trust the directory. It never saves that answer for your home directory, so run it in a project folder. - **A process that stays up:** when `claude` stops, the session goes offline until you bring it back. It needs no open ports. Claude Code makes outbound HTTPS requests to the Anthropic API and polls for work, so it runs behind a firewall unchanged. While it's connected, the transcript is also stored on Anthropic's servers, which is how your devices stay in sync. ## Three ways to start it ```bash claude remote-control --name "my-box" # server mode: waits for sessions from your phone claude --remote-control # a normal session you can also reach remotely ``` The third is a command inside a session you already have: `/remote-control`, or `/rc`, hands the current conversation over. Server mode suits a remote machine. The first run asks `Enable Remote Control? (y/n)` once, then prints a session URL; press the space bar to show a QR code. Two flags are worth knowing. `--spawn worktree` gives each new session you start from your phone its own git worktree, and `--permission-mode` sets the mode those sessions start in. ## Find it on your phone Open the Claude app and tap **Code**. Remote Control sessions are in the list, with a computer icon and a green dot while they're online. You can also scan the QR code, or open the session URL in any browser. If you don't have the app yet, run `/mobile` in Claude Code for a QR code that leads to the right app store. For long tasks, turn on push notifications. In Claude Code, run `/config` and enable **Push when actions required** for permission prompts and questions, or **Push when Claude decides** for updates such as a finished task. ## Keep the process alive on a remote machine The docs give the rule for remote machines directly: start `claude` inside tmux or screen, so the session survives when your SSH connection ends. ```bash ssh dev@203.0.113.10 tmux new -s phone -c ~/work/myapp claude remote-control --name myapp # answer its first-run questions, then press Ctrl-b d to detach ``` Two limits apply to server mode. If the machine stays up but loses the network for roughly ten minutes, the process exits, and you start it again. If you stop the server yourself, running `claude remote-control` again in the same folder brings its sessions back for about four hours; after that it starts a new session. Sign-ins expire too. Claude Code warns you three days before yours does, and a Remote Control session that outlives its sign-in stops making progress until you log in again ([authentication docs](https://code.claude.com/docs/en/authentication)). ## How shedix sets it up Every shedix machine has Claude Code installed, and its page has a row for Claude Code with a terminal tab and a setup for the Claude app: 1. You sign in to Claude Code in the machine's own terminal, through Claude Code's own flow: open the sign-in page, sign in, then paste the code back. The sign-in stays on the machine. shedix never sees or stores it. 2. shedix starts `claude remote-control` in the machine's `~/work` folder, inside tmux, named after the machine. Claude Code's two first-run questions, whether to turn on Remote Control and whether to trust the folder, appear as buttons. 3. Open the Claude app, tap Code, and the machine is in the list. The machine counts as in use while Claude works, because Claude Code writes its conversation as it goes. When it's waiting for you and nothing else is happening, the machine stops after an hour unused, and the session goes offline with it. Turn on Keep awake for the machine if you want to come back to it from your phone hours later. If it did stop, start it again from the shedix page; its files, the conversation included, are still on the disk. The phone's browser is always a fallback. The machine page and its web terminal work on a phone, so you can type into Claude Code directly when the app isn't an option. ## Codex, in beta shedix also has a beta setup for the ChatGPT app. It signs Codex in with a device code, then runs Codex's `codex remote-control` to show a pairing code you enter in the app. The [Codex CLI reference](https://learn.chatgpt.com/docs/developer-commands?surface=cli) marks that command experimental, and OpenAI's [remote connections guide](https://learn.chatgpt.com/docs/remote-connections) describes phone access from hosts running the ChatGPT desktop app on macOS or Windows. Treat the Linux route as an experiment for now, and keep the web terminal as your fallback. [Close the laptop](/use-cases/close-the-laptop) shows how to move a session from your laptop to a shedix machine, and the [FAQ](/faq) answers the usual questions about sign-ins and phones. [Start a machine](/) to try it.