SSH from Phone in 2026: What Works, What Breaks

Short answer. You can SSH from your phone today on either iPhone or Android, and people do it daily. The three real paths are a polished SSH client (Termius, free tier), a mosh-capable iOS client (Blink Shell, $19.99/year), or a full Android shell with OpenSSH inside it (Termux + openssh-client). What breaks is rarely the client. It's the laptop you SSH into going to sleep, the cellular network handing off mid-edit, and tmux feeling miserable on a glass keyboard. We'll show what works, what doesn't, and where a managed cloud terminal fits.

We wrote this from the train, the same one we always use as a test rig. We have an iPhone 15 Pro and a Pixel 8 in the bag, a laptop on a Tailscale tailnet at home running tmux, and a Cosyra container in the cloud with the same agents pre-installed. Both setups answered the same prompt about a failing test. One needed three pieces of infrastructure to keep working in a tunnel. The other needed an internet connection.

This post was written by the Cosyra team. We compared three honest ssh-from-phone setups against our own product based on hands-on use of both, first-hand reads of mosh.org, the Termius and Blink Shell official sites, the Tailscale docs, and our internal factsheets at .claude/growth/competitor-facts/. Claims and pricing are current as of 2026-05-02.

How does SSH from a phone actually work?

SSH from a phone is a phone-side client app talking to an SSH server on another machine. The phone never runs your code. It runs a terminal that forwards your keystrokes to a Linux box that does. The interesting part is everything else: how the phone reaches the box (Tailscale, port-forward, public IP), what survives a network drop (mosh vs raw SSH), and how the session persists when you switch apps (tmux). The client is the easy part of the stack. Most ssh-from-phone failures are at one of those three other layers.

Three layers, each with a real failure mode:

• Reachability — your phone has to be able to find the target machine. Public IPv4 plus port-forward works and is awful to set up and keep secure. Tailscale is the modern answer: install it on both devices, sign into the same tailnet, ssh to user@machinename from anywhere. Free for personal use up to 100 devices as of 2026-05-02.
• Connection survival — plain SSH uses TCP. When your phone sleeps or hands off from Wi-Fi to cellular, the TCP connection dies and so does your shell. Mosh is the fix. It is "a remote terminal application that allows roaming, supports intermittent connectivity, and provides intelligent local echo and line editing." Mosh uses UDP, keeps state server-side, and reconnects automatically when signal comes back.
• Session persistence — even with mosh, closing the SSH app kills the session. tmux runs server-side, so your shell, your editor, and your long-running agent stay alive in a detached session you can reattach to from any device.

Each of those three pieces does a different job. Skipping one breaks the setup in a specific way: no Tailscale and you're managing port-forwards or paying for a static IP, no mosh and your session dies in subway tunnels, no tmux and your work disappears when you switch to Slack to answer a DM. Practitioners who run this stack daily, like the author of "Agentic coding from anywhere", name all three and call out that the workflow falls apart without any of them.

What SSH clients do people actually use on phones?

Three clients show up in nearly every Hacker News thread on this topic and in every practitioner blog. We've used all three. Here is the honest rundown as of 2026-05-02.

Termius (iOS, Android, macOS, Windows, Linux)

Termius is the most polished cross-platform SSH client we've used. The free Starter tier covers SSH, SFTP, port forwarding, and an AI command autocomplete called Gloria Ops. Pro is $10/month annual for vault sync across devices. Team adds multiplayer terminal sessions at $20/user/month. The killer feature for phones is the encrypted vault: define a host once on your laptop, your phone has it, your iPad has it. Termius is a client though, not an environment. You still bring the server to SSH into.

Blink Shell (iOS only)

Blink Shell is the iOS terminal we recommend if you live on iOS and want mosh. $19.99/year subscription, open-source on GitHub. It supports both SSH and Mosh, has a real Bluetooth keyboard story, and pairs with external 4K displays. The Blink Code product line adds a VS Code experience over SSH or GitHub Codespaces. Blink also operates Blink Build — a managed cloud VM in open beta gated to Blink Plus — for the case where you want the server side included; see our comparison for the trade-offs. Outside Build, Blink Shell is a client, full stop. Like Termius, you need a server with the actual tools installed for it to be useful.

Termux + openssh-client (Android only)

Termux is a different category. It's a real Linux environment on Android, not just an SSH client. Install openssh from APT and you have a full SSH client and server. Install tmux, mosh, git, and node and the phone itself becomes a small Linux box. Termux is Android-only; it was off the Google Play Store from 2020 to 2024 and returned in June 2024 as a separately-versioned official build (Android 11+), while F-Droid and the GitHub releases remain the channels most install guides reference. Two real caveats: Android 12+'s phantom-process killer can terminate long-running sessions (GitHub issue #2366), and the ARM userland breaks the long tail of Linux binaries that assume glibc on x86_64. Our Cosyra vs Termux comparison walks through both in detail.

On iOS there's no Termux. The closest local-Linux option is iSH (Alpine via x86 emulation, free, measurably slow); see our Cosyra vs iSH guide for the measured numbers. For "an SSH client that talks to a real Linux box" Blink or Termius are the right call.

What actually breaks when you SSH from a phone?

Five failure modes show up in practice. We've hit each one. The first three are mostly solvable; the last two are why we stopped using ssh-from-phone as our daily driver.

1. Your laptop goes to sleep

The single most common failure. Your laptop is the SSH server in this setup. When it sleeps, suspends, or hits a kernel update, your phone has nothing to connect to. Wake-on-LAN works on the same network. Across the internet, you can use a "sleep on idle, wake on unicast" pattern, but that requires router configuration and tolerance for the first SSH attempt to fail while the machine wakes up. We've ended a Friday-evening edit because the laptop installed updates and we couldn't reach it from the train.

2. Mobile network handoffs kill the TCP connection

Wi-Fi to cellular, cellular to a different cell tower, walking through a train tunnel — each one breaks the TCP socket that plain SSH rides on. Without mosh, your shell dies, your tmux session is fine on the server but you have to reconnect and reattach. With mosh, the client and server keep a little state machine running and the connection picks itself back up. The mobile-shell/mosh issue tracker documents some edge cases (tmux status-bar rendering, specific terminal apps), but the core reconnect behavior is solid. If you're SSHing from cellular and not using mosh, the tunnel-cell-train-handoff trio will eat your day.

3. tmux on a glass keyboard is genuinely annoying

The HN commenters are right about this one. We've had a Termius session open on the iPhone, fingers hovering, trying to fire Ctrl-b d to detach, and missing the Ctrl by half a key three times. Soft keyboards with a customizable key-row help (Termius and Blink both have one). External Bluetooth keyboards solve it entirely, which is great if you're at a coffee shop with a folding keyboard and worse if you're standing on a crowded subway. Our opinion most ssh-from-phone advocates would push back on: the right answer to "tmux is annoying on glass" is to do less in tmux on the phone, not to perfect the muscle memory. Direct an agent in short prompts. Read diffs. Approve. The character-by-character work belongs at the desk.

4. NAT, public IPs, and the home network are real

If your "server" is a laptop on home Wi-Fi, you have a routing problem. Either you forward port 22 (and now your home router is exposing SSH to the public internet, with all the brute-force scanning that comes with that), or you run Tailscale. We always run Tailscale in this setup; we wouldn't expose port 22. Tailscale removes the routing problem entirely on personal use up to 100 devices as of 2026-05-02. The cost is one more piece of software, one more identity to manage.

5. The agent has to be installed somewhere

The whole point of SSHing from your phone in 2026 is usually to drive an AI coding agent. That agent has to be running on the machine you SSH into. If the laptop is your office machine, the agent isn't installed at home. If you reformatted last weekend, you're reinstalling. If you have three machines (laptop, desktop, VPS), you're maintaining three copies of the agent and keeping them in sync. The "where does the agent live" problem is the one that nudged us toward a managed cloud terminal in the first place. The agents come with the environment.

When is SSH from your phone the right answer?

Three honest cases where ssh-from-phone beats anything we sell:

• You already have the server. If you run a homelab, a personal VPS, or a beefy desktop you're going to leave on anyway, the marginal cost of "SSH into it from my phone" is one Termius license and a Tailscale account. Both are free or close to it. Pay for the laptop power instead of a subscription if that fits your stack better.
• You need full root and a custom kernel module. Cloud containers don't give you that. Cosyra, Codespaces, Replit — none of us do, and we shouldn't. If you're working on kernel drivers or doing low-level systems research, SSH into a machine you control.
• You don't want to trust someone else's container. Reasonable position. We host your code. Some people would rather host it themselves, and ssh-from-phone with Tailscale is the cleanest expression of that preference today.

For everyone else — phone-first developers, people who don't want a laptop fan running 24/7, and the teams who'd rather pay $29.99/month than maintain the SSH+mosh+tmux+Tailscale stack — the calculus changes.

How do you actually set up SSH from your phone?

The honest 15-minute setup. We do this fresh every time we test the workflow on a new device. Three steps, each with a single failure mode.

Step 1: Give the target machine a stable address

Install Tailscale on the laptop or VPS you want to reach and on your phone. Sign in to the same tailnet on both. Now you can ssh user@machine-name from anywhere without port-forwarding, public IPs, or static NAT. Tailscale is free for personal use up to 100 devices as of 2026-05-02.

Step 2: Install an SSH client and add your key

On iOS install Termius (free) or Blink Shell ($19.99/yr, mosh support). On Android install Termius or Termux (then pkg install openssh). Generate an Ed25519 key on the phone, copy the public key into ~/.ssh/authorized_keys on the target machine, and test the connection. We use Ed25519 because it's the current default and the keys are short enough to paste between apps.

Step 3: Run tmux server-side so the session survives sleep

Start a tmux session on the target machine the first time you connect: tmux new -s work. Detach with Ctrl-b d, then re-attach next time with tmux attach -t work. If you swap plain ssh for mosh, the connection itself survives network handoffs; tmux handles app-switch and phone-sleep on top of that. This is the combo every practitioner blog ends up at.

That's the working version. It is not less software than a managed cloud terminal, it is more — Tailscale, an SSH client, a key, tmux, mosh, plus the agent installed on the laptop. The trade-off is real: free or close to it, but only if you already have the server and the appetite to keep it running.

When does a cloud terminal beat SSH from your phone?

The simple framing: ssh-from-phone is a do-it-yourself dev environment. Cloud terminals like the one we ship are the same thing pre-assembled. You're either paying with software you maintain or money you spend.

A few specific places we think the calculus tips toward managed:

• You don't want to keep a laptop awake. If your only "server" is a personal laptop, ssh-from-phone forces it to be powered on, not updating, not in sleep, and on a connection your phone can reach. Our container hibernates after 10 minutes idle and resumes on reopen. That's a different kind of "always available."
• You want the same environment on iPhone, Android, and the web. SSH-from-phone gives you whatever your laptop has. If you switch to a different phone or someone hands you an iPad, you reinstall Termius and re-add the keys. Our container is reachable from any device logged into your Cosyra account, with the same files and the same agents.
• You want Claude Code, Codex CLI, OpenCode, and Gemini CLI ready. These are pre-installed in the container we ship. With SSH-from-phone, they're whatever you set up on your laptop, and you're maintaining four agent installs.

Where we wouldn't sell against ssh-from-phone: anyone who already runs a server, anyone who needs root and kernel access, anyone who really doesn't want their code in someone else's cloud. The SSH path is honest, free or cheap, and well-understood. We have a comparison in the mobile coding terminal pillar that goes deeper into the spectrum.

How do you try Cosyra if you're coming from an SSH workflow?

Same shape as the SSH path, fewer pieces.

1. Install Cosyra from the App Store or Google Play. Sign in with Apple, Google, or email. The app provisions an Ubuntu 24.04 container on first launch.
2. Tap into the container. The agents are already on the path. which claude codex opencode gemini returns four results.
3. Add your Anthropic / OpenAI / Google API key to the container's ~/.bashrc (we don't proxy or meter model billing — you pay the provider directly). Run claude.

No Tailscale, no SSH key copy, no tmux new -s work. The container is the persistence; the phone is the terminal. Sessions hibernate after 10 minutes idle and resume on reopen, so the equivalent of "tmux attach" is reopening the app.

For a deeper walk-through of the agent side specifically, see our Claude Code on phone guide. For the broader landscape of mobile terminal options, the mobile coding terminal pillar maps the whole field.

Frequently asked questions