Is There a Warp Terminal for Mobile? (2026) — iOS, Android, and What to Use Instead

The short answer

No — there is no Warp terminal for mobile. Warp ships for macOS, Windows and Linux only. There is no iOS or Android app, and Warp has never announced one.

What exists on a phone is a browser, and two different things you can reach through it:

1. Warp Drive on the web — view and edit your Workflows, Notebooks, Prompts and session transcripts from mobile Safari or Chrome. You cannot execute anything: there is no shell session behind the web view.
2. Remote Control — publish a running coding-agent session from your Warp desktop to the cloud, then watch and steer it from your phone. The agent still runs on your computer.

Both require a desktop machine that is powered on and running Warp. Neither gives you a terminal in your pocket. If what you need is to SSH into a server from your phone — read logs, restart a service, fix something at 2am — that is a different category of tool, and the rest of this page covers which one and how to set it up.

Where Warp actually runs

Per Warp’s installation docs, the supported platforms are:

Mobile is a long-standing community request rather than a roadmap item. Warp for Mobile (#8037) was opened in November 2025 asking specifically for Android, and was closed as a duplicate of the older Support Android (AOSP) (#3328). There is also #7332, asking for official Android support with Termux compatibility. Duplicates piling onto an old issue is the usual shape of “wanted, not planned.”

What Warp gives you on a phone

Three separate things get called “Warp on mobile,” and they differ wildly in what they can actually do.

Warp Drive on the web is the officially documented mobile surface. It supports iOS Safari 15+, Android Chrome 58+ and Samsung Internet 7.2+, with touch scrolling, double-tap to select and long-press context menus. You can read and edit Workflows, Notebooks and Prompts, and read session transcripts. The documented exception is the important one: you cannot execute a command from a workflow or notebook, because there is no shell session running on the web. It’s a knowledge base you can open on a train, not a terminal.

Community Android ports do exist — there are AGPL-licensed projects on GitHub and F-Droid that reimplement Warp’s block-style command UI on Android, generally bundling a Termux runtime underneath for the actual shell. They are not Warp builds and carry no relationship to the company. They also inherit Termux’s model: you get a local Android shell, which is a genuinely useful thing but is not your production server. If your goal is operating a remote host, a port of Warp’s UI over a local shell doesn’t get you closer.

Remote Control, in detail

This is the one worth understanding properly, because it’s the closest Warp comes to a mobile story and it’s frequently misdescribed.

Remote Control publishes a running third-party CLI agent session — Claude Code, Codex, OpenCode and others — from your Warp desktop to the cloud, as a link. Warp’s own announcement pitched it as taking “any coding agent on the go,” with live cursors when teammates join the same conversation.

From a phone browser you get:

• The full agent view — prompts, responses, thinking states, tool use, planning steps, terminal output.
• View access: anyone with the link can watch.
• Edit access: send input, approve commands, or redirect the agent.
• No install. It’s a web page.

Warp’s docs draw a line between this and Session Sharing: sharing is for live collaborative work like pair debugging, while Remote Control is for async monitoring and steering when you’re away from your machine. That framing is accurate, and it’s also the limitation.

What it can’t do, and why that matters. The session lives on the machine you started it on. Warp is the relay, not the host. So:

• Your laptop sleeps in your bag, the session goes with it.
• If the thing that broke is a server, and that server isn’t the machine running Warp, Remote Control has nothing to publish.
• You can’t start something new from the phone. You can only steer what you already left running.
• It’s tied to your Warp account and its credits. The Free plan grants 150 AI credits/month for the first two months and 75/month after; Build is $20/month with 1,500 credits (Warp’s pricing announcement). Bring-your-own-key against OpenAI, Anthropic or Google routes around credit consumption and bills you at the provider instead. These numbers have moved more than once — take the current ones from Warp’s own pricing page rather than from here.

Compare that with SSH into a VPS from your phone: the box is already up because it’s a server, work survives in tmux whether or not any of your devices are awake, and you can start anything rather than only resume something. Remote Control is a good answer to “is my refactor done yet.” It is not an answer to “the site is down and I’m on a train.”

Why there’s no Warp mobile app

Not a mystery, and not laziness. Three structural reasons.

Warp assumes a local shell. The whole design — blocks, command detection, an input editor that behaves like a code editor — is built around a shell process on the same machine, hooked at the shell level. iOS won’t let an app spawn arbitrary processes with a JIT-capable runtime; Android will, but only inside the app’s own sandbox, which is precisely what Termux is. A faithful mobile Warp would be either a very different product or an app that can only talk to itself.

The UI is a desktop UI. GPU-rendered blocks, multi-pane layouts, a modal command palette, and an input area that assumes a full keyboard with modifiers. On a 6-inch screen with a software keyboard, most of what makes Warp Warp either doesn’t fit or has nowhere to bind.

The company went a different direction. Through 2026 Warp repositioned from “terminal” toward an agentic development environment — agent management, Warp Drive, and universal agent support that hosts other vendors’ agents inside Warp. In that world the natural mobile answer is “a web view onto an agent running on a real computer,” which is exactly what shipped. Coherent product decision. Just not a terminal.

Warp features, mapped to mobile

If you’re here because you like specific Warp things, here’s where each one lands.

The second row matters most. Agent mode is Warp’s marquee feature and it has the worst mobile story — not because of Warp, but because approving an agent’s commands on a phone screen is exactly where review quality collapses. That case in full: AI agent terminal vs AI assistant.

What to use instead

Pick by what you’re trying to do, not by which app has the closest-looking UI.

Disclosure: TermAI is our product, so weigh that accordingly. The checkable facts: iOS and Android, unlimited SSH and SFTP on the free tier with 5 AI requests a day, Pro at $2.99/month, Tailscale built into the app rather than a second app you juggle in the background, and AI that writes a command with a Run button rather than executing on its own.

That last property is the deliberate one. On a phone, suggest-then-confirm beats act-then-apologise, because the screen you’d review a destructive command on is four inches wide and you’re probably walking.

The setup that replaces it

If the honest version of “Warp on my phone” is “AI-assisted terminal work while I’m away from my desk,” here’s the whole thing.

1. Make the box reachable. Tailscale on the server and the phone puts both on a private network with no port forwarding, no dynamic DNS, and no dependence on your carrier’s CGNAT behaviour:

# on the server
curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up

Install Tailscale on the phone, sign in with the same account, and the server is reachable by its Tailscale name from anywhere. Auth trade-offs are in Tailscale SSH, explained.

2. Use a key, not a password. Generate on the phone, install the public key on the server. SSH key vs password covers why this isn’t optional on a device that lives in your pocket.

3. Keep work alive in tmux. This is the piece that makes a phone viable at all — a locked screen or a Wi-Fi-to-LTE handoff sends SIGHUP and kills anything not detached:

tmux new -As work      # create, or attach if it exists
# ... start whatever long-running thing ...
# detach: Ctrl-b then d
tmux attach -dt work   # later, from the phone

The -d matters: tmux sizes every window to the smallest attached client, so attaching from a phone without it squashes your desktop session to phone width. Two lines in ~/.tmux.conf on the server earn their keep:

set -g mouse on
set -g history-limit 50000

Mouse mode is the single biggest quality-of-life win on a touchscreen — you scroll output with a finger instead of entering copy mode. Alternatives to tmux are compared in keeping a process running after SSH disconnects.

4. Add mosh if your connection is bad. Mosh survives IP changes; SSH re-handshakes on every one. Use it with tmux, not instead of it — mosh keeps the link alive, tmux keeps the session alive when the link dies anyway. mosh vs SSH.

That stack gives you something Warp’s mobile surfaces structurally can’t: your server, reachable directly, with sessions that outlive every device you own.

FAQ

Is there a Warp terminal app for iPhone or Android? No. Warp ships for macOS, Windows and Linux only. Mobile requests exist on the public tracker — #8037 (November 2025) was closed as a duplicate of the older #3328 — but no app has been announced.

Can I use Warp in a mobile browser? Partly. Warp Drive on the web runs on iOS Safari 15+, Android Chrome 58+ and Samsung Internet 7.2+, and lets you view and edit Workflows, Notebooks, Prompts and session transcripts. It cannot run a command — there’s no shell session behind the web view.

What is Warp Remote Control? A way to publish a running CLI-agent session (Claude Code, Codex, OpenCode…) from your Warp desktop as a link you can open on a phone. You see the agent’s output and, with edit access, can send input or approve commands. The agent runs on your computer, not your phone.

Does Remote Control need my computer to stay on? Yes. The session lives on the machine that started it; Warp relays it. Sleep the laptop and the session goes with it — which is why SSH into a server that’s already meant to stay up is the more robust pattern.

Is there an unofficial Warp for Android? Community ports exist that reimplement the block-style UI over a bundled Termux runtime. They’re independent projects, not Warp builds, and they give you a local Android shell rather than a route to your servers.

What should I use if I want an AI terminal on my phone? An SSH client with an assistant, since phone terminal work is remote work by definition. TermAI on iOS and Android, or Termius if you want the same profiles on desktop. Full field map: AI terminal tools compared.

The question behind “is there a Warp for mobile” usually isn’t really about Warp. It’s “can I do terminal work when I’m not at my desk” — and that answer has been yes for years, just not via a terminal emulator installed on the phone. It’s via a phone that’s a good client for machines already running.

Sources: Warp installation docs, Warp Drive on the web, Warp Remote Control, Warp pricing changes, warpdotdev/warp #8037, #3328.