Guide
How to use OpenCode from your phone in 2026
This guide reflects first-party and project documentation reviewed on August 25, 2026. OpenCode still ships no official native phone app, but an independent Android client now exists alongside SSH, browser, cloud-workspace, and multi-harness approaches. Here are five practical options and the trust boundary behind each one.
The 5 ways developers actually do it
Option 1
SSH into your machine from a terminal app
The baseline that has always worked: run OpenCode inside tmux or screen on your laptop, then SSH in from a mobile terminal such as Termius or Blink Shell and reattach. Nothing new to install on the host, and it works with any agent. The cost is ergonomics — a TUI built for a 100-column terminal is painful on a 6-inch screen, diffs are hard to read, and you are typing shell commands on glass.
Best for Developers who already keep a hardened SSH setup and want zero extra moving parts.
Visit →Option 2
Warp Remote Control
Warp added remote control of agent sessions, covering Claude Code, Codex, OpenCode, and Gemini CLI. Access is through the browser rather than a native mobile app, so there is nothing to install on the phone. You are inside the Warp ecosystem, and the experience is a responsive web view rather than a purpose-built mobile UI.
Best for Warp users who want browser access without adding another vendor to the stack.
Visit →Option 3
Cosyra
Gives each user an Ubuntu 24.04 container on Azure with Claude Code, Codex CLI, OpenCode, and Gemini CLI pre-installed, plus native iOS, Android, and web clients. Because the container is the dev environment, your laptop does not need to be awake. The tradeoff is that your code is checked out and executed on their infrastructure rather than your machine.
Best for Developers who want OpenCode running somewhere that never sleeps and accept cloud-hosted code.
Visit →Option 4
OpenCode Mobile for Android
Independent, community-built Android client in Google Play beta and on GitHub under Apache-2.0. It connects to an OpenCode server you control and supports tasks, approvals, changed-file review, terminal commands, workspaces, voice, and usage visibility. There is no iOS build. You are responsible for authentication and a secure HTTPS tunnel, reverse proxy, or private-network path to the server.
Best for Android users who want an OpenCode-specific open-source client and are comfortable securing server access.
Visit →Option 5
Sesori
Mobile cockpit for OpenCode, Codex, Cursor, Claude Code, Pi, OMP, and Hermes on iOS and Android. The Bridge runs beside OpenCode on your computer, while ordinary session traffic crosses an end-to-end encrypted relay. Review diffs, approve permissions, send voice input, queue messages, run parallel sessions, and receive push notifications. Voice transcription and other invoked hosted features have separate data paths documented in the Privacy Policy. Your machine must remain running.
Best for Developers who want a purpose-built mobile UI for OpenCode without moving their code off their own machine.
Learn more →