Yes. CLIAnywhere lets you access a terminal session running on your Windows, macOS, or Linux PC from an iPhone, Android device, or web browser. The session keeps running on your PC even when the mobile connection is interrupted, so you can reconnect and continue the same shell — with no port forwarding or public IP address required.
All commands run on your PC. The CLIAnywhere daemon on the computer owns the shell session; the phone (or browser) only sends keystrokes and displays output. Nothing is executed on the phone, so the session is not tied to the phone staying online — close the app, lock the screen, or lose signal, and the shell keeps running on the PC until you come back.
The daemon on your Windows, macOS, or Linux computer runs the shell and every command you send.
Peer-to-peer DTLS when possible, encrypted WSS relay otherwise — encrypted end-to-end with AES-256-GCM either way.
Attach from iPhone, Android, or the Web App and interact with the same session from anywhere.
A native app or a browser — whichever device you have in hand attaches to the same session.
The iOS client attaches to any computer linked to your account — so it works for accessing a Mac terminal, a Linux box, or a Windows PC from your iPhone. Available on the App Store — see the download page.
The Android client is available on Google Play. Sign in with the same account as the daemon on your PC, pick the computer, and you are in its shell.
No install at all: open webapp.clianywhere.com in a browser, sign in, and select your computer. Useful on a borrowed machine, or to continue a session from another computer.
SSH client apps for iOS and Android exist and work well when the target machine is reachable — a cloud server, for example. The catch is session handling on a mobile network: each SSH connection creates a new session, and when the connection drops, that session and whatever was running in it usually end with it. Reaching a home PC over SSH also typically needs port forwarding, a VPN, or a public IP.
CLIAnywhere takes a different route: the session lives on your PC under the daemon, the phone attaches to it, and connections go over outbound P2P DTLS or an encrypted relay. Drop your connection and the session is unaffected — reopen the app and you are back in the same shell.
Say a fix landed while you were away from your desk, and you want it deployed before you get back. You open CLIAnywhere on your phone, pick your PC, and type into the shell that is already running there:
# on your phone, running in the shell on your PC $ git pull Already up to date. ... 1 file changed, 12 insertions(+) $ sudo systemctl restart myapp $ systemctl status myapp --no-pager Active: active (running) since 14:02:07
Twenty seconds of typing on the phone, and the deploy is done — no laptop, no VPN, no open ports. If the phone loses signal mid-command, the session on the PC continues, and you reconnect into the same shell.
What is supported, without the marketing.
| Windows host | Yes |
|---|---|
| macOS host | Yes |
| Linux host | Yes — desktop UI or headless CLI |
| iOS client | Yes |
| Android client | Yes — Google Play |
| Web client | Yes — webapp.clianywhere.com |
| Shells | bash, zsh, fish, sh, cmd, pwsh, powershell |
| Persistent sessions | Yes |
| Desktop–mobile session switching | Yes |
| File browser and download | Yes |
| Localhost / LAN web access | Yes |
| P2P direct connection | Yes — DTLS |
| Encrypted relay fallback | Yes — WSS |
| End-to-end encryption | SPAKE2 + AES-256-GCM |
| Port forwarding / public IP required | No |
| Open-source daemon | Yes |
| Account model | One account, multiple PCs, per-PC local Security Code |
Set up the daemon once, then attach from iPhone, Android, or any browser.