Ways to Remote-Control Claude Code
Compare five ways to remote-control Claude Code: native Remote Control, Channels, SSH with tmux, browser terminals, and Chatcode.
“Remote control” can mean a full terminal, a mobile chat, or a first-party view of a session that is already running. Those interfaces solve different problems, even though all of them can put Claude Code within reach of a phone.
Quick answer
- Start with Anthropic Remote Control for a first-party mobile or web interface.
- Use Channels when Telegram or another event source is the desired input.
- Use SSH + tmux for standard, portable, full-shell access.
- Use a browser terminal behind a private tunnel when installing an SSH client is undesirable.
- Consider Chatcode when one browser/Telegram layer needs to cover Claude Code and other terminal agents.
In every host-based approach, the computer running Claude Code must remain awake and connected.
The options at a glance
| Approach | Phone interface | What stays running | Network/trust boundary | Agents |
|---|---|---|---|---|
| Claude Remote Control | Claude mobile or web | Claude Code on the host | Anthropic relay | Claude Code |
| Claude Channels | Telegram or another channel | Claude Code plus channel plugin | Anthropic plugin and channel provider | Claude Code |
| SSH + tmux | Mobile terminal | Host, SSH, and tmux session | Your SSH/VPN setup | Any shell agent |
| Web terminal + tunnel | Mobile browser | Host, terminal server, and tunnel | Terminal, proxy/tunnel, and authentication | Any shell agent |
| Chatcode | Browser terminal and Telegram | Connected host and gateway | Chatcode gateway and relay | Supported terminal agents |
1. Claude Remote Control
Remote Control connects a host-side Claude Code process to Claude on the web or the iOS/Android app. The repository, tools, and credentials stay on the host. The phone is a remote interface and can receive notifications when work needs attention.
This is the lowest-setup option if you already use Claude’s apps. It is Claude-specific, and the local process still has to stay alive. A laptop that sleeps is not an always-on agent host.
2. Claude Code Channels
Channels lets an external service send events into a running Claude Code session. The official Telegram plugin supports paired, allowlisted chats and can relay supported permission requests with Allow and Deny controls.
Channels fits short instructions and notifications better than terminal navigation. It also adds the security model of the channel provider and bot token. The detailed setup is in How to Connect Claude Code to Telegram.
3. SSH with tmux
SSH gives you the real shell. tmux keeps a named session alive when the
network drops:
ssh dev@example-host
tmux new -As claude
This works with any terminal tool and has no product-specific relay. It also makes you responsible for keys, host hardening, reachability, and a dense TUI on a small screen. A VPN or overlay network can keep SSH off the public internet.
4. A browser terminal behind a tunnel
A terminal server such as ttyd can put the shell in a mobile browser. Keep it
behind strong authentication and a private network or an outbound tunnel
rather than exposing the terminal directly.
This is convenient across devices but creates more pieces to secure: terminal server, reverse proxy or tunnel, session cookies, origin rules, and host permissions. If the page can execute shell commands, treat account takeover as server compromise.
5. Chatcode
Chatcode connects a server to a browser terminal and Telegram through an outbound gateway. It supports sessions for Claude Code, Codex, Gemini, and OpenCode, which is useful when the remote-access layer should not belong to one agent vendor.
The cost of that convenience is another service and relay in the trust model, plus the server you still maintain. It is a better fit for a consistent multi-agent interface than for someone who only needs occasional access to one Claude session.
A practical decision sequence
- Do you only need Claude and like the Claude app? Try Remote Control.
- Is Telegram itself the requirement? Try the official channel before adding another service.
- Do you need an unrestricted shell and value portability? Use SSH and tmux, preferably over a private network.
- Is a browser mandatory? Put a terminal behind carefully configured authentication and a tunnel.
- Do several agents need the same browser and Telegram workflow? Evaluate Chatcode, including its relay and server-management trade-offs.
For a deeper infrastructure comparison, see Chatcode vs. DIY tmux and SSH.
Frequently asked questions
What is the simplest way to use Claude Code from a phone?
Anthropic’s Remote Control is the shortest first-party path if the Claude app or web interface works for you. The Claude Code process and its host still need to remain available.
Can I run Claude Code on a remote machine?
Yes. Install and run Claude Code on an always-on server or another computer, then reach that host through Remote Control, SSH with tmux, a browser terminal, Channels, or another remote layer. The remote host still needs to remain awake, connected, and secured.
Is a web terminal safer than SSH?
Not inherently. Either can be secure with strong authentication and a private network or outbound tunnel. A web terminal exposes a shell through a web stack, so its proxy, authentication, cookies, and origin rules all need scrutiny.