Claude Code on Your Phone: Remote Control vs SSH vs Full IDE
Three ways to run Claude Code on your phone: official Remote Control, SSH with Tailscale and tmux, or a full IDE. Setup, visibility and reliability compared.
The Coder IDE team · · 7 min read
Claude Code runs on your computer, but the moments you want to check on it rarely happen at your desk. There are now three serious ways to reach it from a phone, and they solve different problems. This post compares them on setup, what you can see, how they handle several sessions, and what happens when the connection drops, then gives an honest recommendation for each kind of user.
Three ways to reach Claude Code from a phone
Official Remote Control. Anthropic's Remote Control links a Claude Code session on your machine to claude.ai/code or the Claude app. Claude keeps running locally. Your phone is a window into the conversation.
SSH, Tailscale and tmux. The classic route: put your computer and phone on the same private network with Tailscale, SSH in from Termux on Android or an SSH app on iOS, and run claude inside tmux so it survives disconnects. This walkthrough is a good reference, and Builder.io's guide covers similar ground.
A browser IDE connected to your computer. Run the full editor on your machine and open it on your phone. Coder IDE does this with Microsoft's VS Code server, and adds a layer for Claude Code sessions: notifications, approvals and reviews. Other browser IDE setups work too, but most of them leave the Claude side to you.
All three keep your code on your own machine. None of them works if that machine is switched off.
Setup effort
Remote Control is the quickest if you already have an eligible plan. Run claude --remote-control or type /remote-control in a session, and scan the QR code with your phone. It needs a Pro, Max, Team or Enterprise plan. API keys aren't supported, and on Team and Enterprise an Owner has to enable it first.
SSH and tmux takes about 20 minutes the first time, by the walkthrough author's estimate. Install Tailscale on both devices, Termux from F-Droid (the Play Store build is outdated), openssh, then tmux on the computer. Add SSH keys, disable password login, and consider mosh if your connection is flaky. Every step is well documented. There are just several of them, and phone-friendly tmux keybindings are a project of their own.
Coder IDE is one install command on the computer, then you click Sign in in the desktop app and confirm the code from a browser you're signed in to. The machine shows up on your dashboard. On the phone you open the site or the Android app. No port forwarding, VPN or certificates, and it works behind NAT and firewalls. You can see the steps in how it works.
What you can actually see
This is where the three approaches differ most.
Remote Control shows the conversation as it happens, and you can send messages, attach photos and files, and answer permission prompts. In a git repository, a diff pane shows your changes. Some commands, like /plugin and /resume, only work in the local terminal. You don't get a file tree, an editor or a terminal of your own.
SSH shows you exactly what the terminal shows: the Claude Code TUI, plus a shell for anything else. That's powerful, and it's also everything squeezed into a phone-width terminal. Reading a 300-line diff there is possible but tiring.
Coder IDE gives you a session view and the full editor behind it. Each session's changes can be reviewed file by file, you can comment on lines and send all your comments to Claude in one message, and Open in VS Code jumps to the exact file and line. When Claude starts a dev server, turn on Allow preview for its port in the Ports panel and you get a private link, which only opens for you, to check the running app on the same phone. The editor itself is real VS Code, with your extensions, settings and terminal.
Multiple sessions and multiple computers
If you run one session on one laptop, skip this section. If you run three agents across a desktop and a laptop, it matters most.
Remote Control gives each interactive claude process one remote session. Server mode, claude remote-control, can run many sessions from one process and can put each in its own git worktree. Sessions appear in the claude.ai/code session list, named after the machine by default.
SSH scales the way tmux scales: one window per session, one SSH connection per computer. It works, but you're the one remembering which pane on which machine is waiting.
Coder IDE lists every Claude Code session on every computer you've connected, whether it started in a terminal, in VS Code or in the background. The list is grouped by what needs you, so a session waiting on approval sits above one that's still working. You can start a new session in any project from your phone, and keep several projects open at once. Managing sessions across several computers covers that workflow in detail.
When the laptop sleeps or the network drops
Phones lose signal, and laptops close. Here's how each option copes.
Remote Control handles this well. If your laptop sleeps or the network drops, Claude Code reconnects when the machine comes back online. An interactive session keeps retrying through an outage. Server mode gives up after roughly ten minutes without network and exits, so you restart it. If you close the terminal or quit the app running claude, the session goes offline until you bring it back.
SSH depends on tmux. Claude keeps running inside tmux when your SSH connection dies, and you reattach later. Plain SSH stalls on network changes, and mosh smooths that over. If the computer sleeps, everything pauses.
Coder IDE keeps Claude Code working when your phone sleeps, you switch apps, or your connection drops. When you come back, the session is where Claude left it. On the same home network the editor connects directly to your computer and falls back to the relay automatically when you leave. If the computer itself sleeps, Claude stops, the same as with every other option.
Which to pick
| Remote Control | SSH + Tailscale + tmux | Coder IDE | |
|---|---|---|---|
| Setup | QR code, a minute | About 20 minutes | One install command, approve the device |
| Cost | Included with Pro, Max, Team, Enterprise (no API keys) | Free tools | Free for one computer, Pro $12/mo |
| See the conversation | Yes | Yes, in the terminal | Yes |
| Diffs | Diff pane | Terminal only | File by file, with line comments |
| Full editor and terminal | No | Terminal only | Yes, real VS Code |
| Dev server preview | No | Run with --host, open the IP |
Private preview link for ports you allow |
| Many sessions, many computers | Server mode per machine | tmux per machine | One list across all machines |
| Push for approvals | Yes | Add your own hook | Yes, approve from phone or browser |
Honest recommendations:
- Choose Remote Control if you're on a Claude subscription, mostly steer one session at a time, and don't need an editor on the go. It's official, fast to set up and keeps improving.
- Choose SSH and tmux if you live in the terminal, want zero new services, and don't mind the setup. It's the most flexible option, and it costs nothing.
- Choose a full IDE like Coder IDE if you want to read and fix code from your phone or tablet, preview the app Claude is building, and track sessions on more than one computer from one place.
You can also combine them. Plenty of people keep Remote Control on for quick replies and open the full editor when a change needs a real look.
Wrap-up
The question isn't whether you can reach Claude Code from your phone. All three options do that. The question is what you need to see when you get there: a chat, a terminal, or the whole project. Pick the lightest option that shows you enough to make good decisions.
If permission prompts are what keep stalling your sessions, read how to approve Claude Code permissions from your phone next.
Start free. The free plan covers one computer, and Pro is $12 a month for unlimited devices.
