Skip to content

OpenCode on Android: 4 Real Ways to Run It

Updated 9 min read By Adam Roman, Co-founder of Cosyra

You can run OpenCode on Android, but not the way most install guides imply. There is no native Android app, and unlike Claude Code or Gemini CLI, a plain npm i -g opencode-ai inside Termux does not work reliably: the launcher misdetects the Termux environment and hands Android-arm64 a Linux-x64 binary. So "OpenCode on Android" means one of four real paths: a cloud Ubuntu container with OpenCode pre-installed (Cosyra on Google Play, where you tap the OpenCode shortcut), the third-party guysoft/opencode-termux native aarch64 build that runs in Termux with no chroot, a Termux proot-distro chroot on-device, or SSH from Termux into your own always-on box. This guide walks each one with the honest trade-offs.

I took the Cosyra steps and screenshots below in the Cosyra 2.9.0 iPhone app on November 3, 2026. The Android app has the same screens. The OpenCode reply and provider screens are OpenCode's own and date from October.

This is the Android-specific companion to our OpenCode on your phone walkthrough (which covers iPhone and Android generically), with a tablet sibling in OpenCode on iPad. What changes on Android is that Termux is a genuine on-device option, unlike on iOS, but OpenCode is the one agent of the four where the Termux story is still broken, which is the part most posts get wrong. The siblings to this guide are Claude Code on Android and Gemini CLI on Android, and all three feed into our Coding on Android pillar, which maps out everything the OS can run as a dev environment. For the broader picture across all four mobile AI agents, see AI coding agents on mobile. One agent worth flagging here: Kilo CLI is built on OpenCode, so it inherits the same Termux misdetection we describe below. We have not tested @kilocode/cli in Termux ourselves, and the clean path is the same cloud container or proot-distro chroot. See Kilo CLI on your phone.

Diagram of OpenCode on Android as of 2026-10-28: upstream OpenCode 1.x (v1.19.5) and OpenCode 2 (v2.2.0) both ship no Android build, Bun has official Android builds since v1.3.14, and four paths run OpenCode from an Android phone: Cosyra cloud container, the third-party opencode-termux native build, Termux with proot-distro, and SSH to your own box.
The OpenCode-on-Android landscape, verified 2026-10-28 against the GitHub releases for anomalyco/opencode, guysoft/opencode-termux, and oven-sh/bun, plus the npm registry metadata for opencode-ai and @opencode/cli.

Quick decision. Jump to the part that matches you:

  • You want OpenCode running in minutes with nothing to babysit. A cloud container runs the real binary and you open it with one tap in the Android app. Cosyra setup ↓
  • You want free and on-device, with no chroot. A community build runs OpenCode natively in Termux. Native Termux build ↓
  • You want free and on-device, with a full Linux userland. Termux plus proot-distro runs OpenCode in a chroot. Know the setup cost first. Termux reality ↓
  • You already keep a box awake. SSH into it from Termux and run OpenCode there. SSH path ↓

Why does plain Termux break OpenCode on Android?

Plain Termux breaks OpenCode because the launcher picks the wrong binary. OpenCode is distributed as prebuilt binaries via npm optionalDependencies, one per platform and arch. An opencode-android-arm64 binary was added after the old postinstall failure (issue #12515) was fixed, so installs no longer hard-fail. But the launcher still misdetects Termux as plain Linux and tries to run the Linux-x64 build on an Android-arm64 device, which fails with an "incompatible binary" error. That is anomalyco/opencode issue #21043, opened 2026-04-04 and auto-closed as not-planned on 2026-07-03 for inactivity, not fixed.

The fix that would have helped, PR #21106, "allow opencode CLI to run in Termux (remove hard exit)", was closed without merging. And the native-Termux feature request (#22805) was closed without a maintainer commitment. That request is worth reading, because the person who filed it points out the thing we keep running into: Claude Code and Gemini CLI both run on Termux, and OpenCode is the holdout that needs a workaround. OpenCode the project is great: 222,775 GitHub stars as of 2026-10-28, latest 1.x release v1.19.5 on 2026-10-28, MIT-licensed, multi-provider. The Termux launcher path is just the rough edge.

One thing changed since our last check. Anomaly now runs two release lines. OpenCode 1.x still publishes as opencode-ai on npm (v1.19.5 is the latest tag as of 2026-10-28). OpenCode 2 shipped v2.0.0 on 2026-09-11 as a separate package, @opencode/cli, with its own installer and a "Migrate from V1" docs track; v2.2.0 landed 2026-10-27. We read the v2 package metadata on the npm registry: it declares os: darwin, linux, win32 and ships no Android binary, so OpenCode 2 does not change the Termux picture. Both lines still need one of the four paths below on a phone.

Here is an opinion the on-device purists will push back on: for OpenCode specifically, fighting the Termux misdetection on a phone is not worth it when the chroot or a cloud container both run the real binary cleanly. We spent an evening on the couch getting plain Termux to load the right arch binary and gave up; the proot-distro route worked, and the cloud container worked with no setup at all. "On-device or nothing" is a principle, not a workflow.

What are the four real ways to run OpenCode on Android?

There are four real ways to run OpenCode from an Android phone as of 2026-10-28: Cosyra (cloud container with OpenCode pre-installed), the third-party guysoft/opencode-termux native aarch64 build, Termux with proot-distro (an on-device Debian/Ubuntu chroot), and SSH from Termux into a box you own. We walk each below. We listed only three here until 2026-07-20, which was our error. The native build has existed since April 2026 and we were tracking only the upstream repo's issue tracker, where it does not appear.

1. Cosyra (cloud container, native Android app)

This is what we build. The Cosyra Android app opens a persistent Ubuntu 24.04 x86_64 container reached from any Pixel, Galaxy, OnePlus, Nothing, or foldable. OpenCode is pre-installed alongside Claude Code, Codex CLI, and Antigravity CLI on Node 20+. Because the container is glibc x86_64, the opencode Linux-x64 binary is the correct one, so the Termux misdetection in #21043 and the older arm64 postinstall failure simply do not happen. You get 30 GB of persistent storage, session hibernation that resumes exactly where you left off, and the same container is reachable from iPhone, iPad, and a browser. OpenCode starts on a free model. When you want your own, run /connect and that provider bills you directly. We do not proxy or meter your model calls.

2. guysoft/opencode-termux (native aarch64, on-device, free)

The one most guides miss, ours included until this update. opencode-termux is an MIT-licensed build system that cross-compiles OpenCode to Android aarch64 so it runs directly in Termux with no chroot. The hard part it solves is the runtime: OpenCode compiles to a standalone binary via Bun, and the stable build line cross-compiles a patched Bun from source, WebKit/JavaScriptCore engine included. Release v0.2.1 (2026-06-25) ships OpenCode 1.17.9 three ways, and the pacman and deb packages pull in ripgrep for you:

opencode-termux: native install

# Option 1: pacman (recommended on Termux)

$ curl -LO https://github.com/guysoft/opencode-termux/releases/latest/download/opencode-aarch64.pkg.tar.xz

$ pacman -U opencode-*-aarch64.pkg.tar.xz

# Option 2: deb

$ dpkg -i opencode-aarch64.deb

# then, either way:

$ opencode

One correction worth making since we are citing this project: its README says Bun marked Android support "not planned" and links Bun issue #9. We checked that issue on 2026-07-20 and it is an unrelated 2022 ByteBuffer item, closed as completed, so do not repeat that citation. We also have to correct ourselves here. Until this update we wrote that Bun has no official Android target. That was wrong. Bun's own GitHub releases have shipped bun-linux-aarch64-android builds since v1.3.14 (2026-05-13), and every release since, through v1.4.4 on 2026-10-22, carries them. We checked on 2026-10-28.

That official target is what the project's newer build line uses. Alongside the stable opencode package, opencode-termux now publishes opencode2, an OpenCode 2 build that its README says is built on "official Bun 1.4.2 android target". Its v1.0.3 release (2026-10-15, still marked pre-release, with release candidates through rc3 on 2026-10-18) fixes a crash where Android's seccomp policy killed Bun with Bad system call (exit 159) by bundling a patched Bun. It installs as a separate opencode2 command and never overwrites the stable opencode. We would treat it as a preview: the stable line is still the one to install if you want something that has been out for months rather than days.

3. Termux + proot-distro (on-device, free)

Termux is an open-source (GPLv3) Android terminal emulator with a real package manager. Because plain Termux misdetects the OpenCode arch (issue #21043), the on-device path that keeps you on the current upstream release is proot-distro: install a Debian or Ubuntu chroot inside Termux, which is a real glibc Linux userland, then install Node 20+ and npm i -g opencode-ai inside it. If you want the full rundown of the chroot path versus UserLAnd versus a cloud x86_64 container, see Linux container on Android.

4. SSH from Termux into your own box

The classic remote route. Install OpenCode on an always-on Linux box or a VPS (Hetzner, Scaleway, DigitalOcean) with npm i -g opencode-ai, then ssh in from Termux inside a tmux session and run opencode. The agent runs on the host; the phone is just the terminal. You can also drive opencode serve over the connection if you prefer the HTTP API to the TUI.

How do you set up OpenCode on Android with Cosyra?

Install Cosyra from Google Play, start your workspace and tap the OpenCode shortcut. OpenCode is already installed and opens on a free model, so the first prompt needs no API key. It takes about three minutes.

Step 1

Install Cosyra from Google Play

Install Cosyra from the Google Play Store. It runs on Pixel, Samsung Galaxy, OnePlus, Nothing and other phones on Android 9 or later. Sign in with Apple, Google, GitHub or email, then pick a plan: Core or Pro.

The app opens on Terminals. On a new account the chip next to the title says Not started. Tap Start your workspace once and it turns Awake.

Cosyra Terminals screen: workspace Awake, the Your shortcuts row and the Home project

Step 2

Tap the OpenCode shortcut

The Your shortcuts row holds Claude Code, Codex, Cursor, Grok, Antigravity and OpenCode. Swipe it to the left until you reach the end and tap OpenCode. It opens in a terminal in your workspace. There is no install step and no sign-in screen. The workspace had OpenCode 2.2.4 when I took these screenshots.

The line under the prompt shows the agent and the model: Build and Big Pickle, a free model from OpenCode Zen. The footer shows the folder you are in.

OpenCode 2.2.4 start screen in a Cosyra terminal, on the Build agent with the Big Pickle model

Step 3

Send a first prompt

Tap the terminal to bring up the keyboard, type a request and press return. I asked for a hello world script in Python and for it to be run. OpenCode wrote hello.py, ran it and printed the output.

The free model has a daily message limit. When you reach it, OpenCode shows Free limit reached with the reset time and points you to /connect and /models.

OpenCode wrote hello.py, ran python3 hello.py and printed Hello, World!

Step 4

Connect your own provider

Type /connect and press return. OpenCode lists its providers, with the popular ones first:

  • OpenCode Zen and OpenCode Go
  • OpenAI, with a ChatGPT plan or an API key
  • GitHub Copilot
  • Anthropic
  • Google

Pick one and follow its sign-in. Then switch models with /models.

OpenCode Connect a provider dialog listing OpenCode Zen, OpenAI, GitHub Copilot, Anthropic and Google

Step 5

Run OpenCode in your own repo

Go back to Terminals, tap New and choose New terminal. I ran opencode --version && node --version && git --version and got OpenCode 2.2.4, Node 22.23.4 and git 2.34.1.

Clone your repository, cd into it and type opencode. This is OpenCode's standard Linux build, so the Termux misdetection in #21043 does not come up.

The toolbar above the keyboard has Esc, Tab, Ctrl and the arrow keys. Tap Ctrl for Shift+Tab, which switches OpenCode between its Build and Plan agents, and Ctrl+C, which interrupts it. OpenCode keeps running in the workspace when you leave the terminal.

Cosyra terminal printing opencode v2.2.4, Node v22.23.4 and git version 2.34.1, with the key toolbar above the keyboard

Step 6

Prefer a chat? Tap Code

Open the sidebar and tap Code. It opens a chat instead of a terminal.

The model chip next to the message box opens the picker. New chats start on OpenCode's free models: GLM-5.3-Flash and DeepSeek V4.1 Flash when I checked.

Cosyra chat model picker listing OpenCode Free models GLM-5.3-Flash and DeepSeek V4.1 Flash

Try Cosyra. Plans start at $20/month. Google Play / App Store / Pricing details

How do the Android options compare?

The four paths line up cleanly against what matters for running an agent from a phone: whether the real binary runs, whether you fight the Termux misdetection, whether it needs another machine, whether it works offline, and whether you are on the current release. The table covers the state as of 2026-10-28.

Feature Cosyra (Android app) opencode-termux (native) Termux + proot-distro SSH to your box
Runs the real OpenCode binary Yes (pre-installed) Yes (native aarch64) Yes (inside chroot) Yes (on host)
Hits Termux misdetection (#21043) No (x86_64 Ubuntu) No (purpose-built for Termux) No (chroot is real Linux) No
Needs another machine No No No Yes (a host)
Works offline No Yes Yes No
Phantom-killer risk None Yes (mitigated) Yes (mitigated) None
Setup time (cold) ~3 min One package install 30–60 min 30–60 min
OpenCode version (2026-10-28) Current upstream 1.17.9 (upstream: 1.19.5) Current upstream Current upstream
Cost (not counting tokens) From $20/mo Free (MIT) Free VPS ~$5–40/mo

Choose Cosyra if you want the current binary with nothing to babysit and the same container across Android, iPhone, iPad, and web. Choose opencode-termux if you want on-device and free with the least setup and 1.17.9 is new enough for you. For most day-to-day agent work it is. Choose Termux + proot-distro if you want on-device and free but need to track upstream releases, and you accept the chroot overhead and the phantom-killer risk. Choose the SSH path if you already keep a box awake. For tmux and TUI ergonomics once you are in a shell, see TUI apps on phone, part of the broader mobile coding terminal pillar. If you are weighing the whole on-device Termux model against a cloud container, our Cosyra vs Termux comparison has the full trade-off list.

Frequently asked questions

Can you run OpenCode natively on Android in Termux?

Yes, using a community build, though not with the official installer. Upstream still misdetects Termux as plain Linux and tries to run the Linux-x64 binary on Android-arm64, giving "incompatible binary" failures; that is issue #21043 (opened 2026-04-04, auto-closed as not-planned on 2026-07-03 for inactivity, not fixed), and PR #21106, which would have removed the hard exit, was closed without merging. What fills the gap is guysoft/opencode-termux, an MIT-licensed project that cross-compiles OpenCode and the Bun runtime itself, including the WebKit/JavaScriptCore engine, to Android aarch64. Its latest stable release v0.2.1 (2026-06-25) ships OpenCode 1.17.9 as a pacman package, a deb, or a standalone zip, and includes fixes for Android 11+ crashes. The trade-off is version lag: 1.17.9 against upstream 1.19.5 as of 2026-10-28, and upstream has also started a separate OpenCode 2 line (v2.2.0). The same project now publishes an opencode2 pre-release (v1.0.3, 2026-10-15) built on Bun's official Android target, which installs side by side with the stable build. If you want to stay on the current version, proot-distro or a cloud container runs the standard Linux build instead.

Why do Claude Code and Gemini CLI work on Termux but OpenCode doesn't?

Because OpenCode ships per-arch prebuilt binaries via npm optionalDependencies and its launcher picks the wrong one inside Termux. The native-Termux feature request (#22805) was opened 2026-04-16 explicitly noting that Claude Code and Gemini CLI both run on Termux while OpenCode needs the proot-distro workaround; it was closed without a maintainer commitment to land native support.

What is the fastest way to get OpenCode on an Android phone?

Install Cosyra from Google Play, sign in, start your workspace and tap the OpenCode shortcut. OpenCode is already installed in a cloud Ubuntu workspace and opens on a free model, so there is no npm install, no proot chroot, no arch misdetection and no API key for the first prompt. Plans start at $20 a month.

Does OpenCode have an official Android app?

No app, but that is a narrower answer than it sounds. The anomalyco/opencode README lists install paths for macOS, Linux (x64 and arm64), and Windows only, and there is no native Android or iOS app. That is still true for OpenCode 2. Whether OpenCode runs on Android at all is a separate question, and the answer is yes: the third-party guysoft/opencode-termux project (MIT, 306 stars, checked 2026-10-28) cross-compiles OpenCode to Android aarch64, and its latest stable release v0.2.1 from 2026-06-25 packages OpenCode 1.17.9 as a pacman package, a deb, or a standalone binary you install inside Termux. That is a native CLI rather than an app, it is community-maintained rather than official, and it trails upstream's 1.19.5. The OpenCode 2 CLI (@opencode/cli, v2.2.0 on 2026-10-27) also ships no Android build: its npm package declares macOS, Linux, and Windows only. Your other routes are a proot-distro chroot, an SSH session to your own box, or a cloud container.

Will proot-distro OpenCode survive when I switch apps on Android?

Not guaranteed. Android 12 and later includes a phantom process killer that can send SIGKILL (signal 9) to background processes Termux spawns, which can end a long OpenCode run when you leave the app. You can mitigate it with device settings or adb, but the failure mode is real. A cloud container sidesteps it because the agent runs server-side, not in a process Android manages.

Is OpenCode free, and what do I pay for on Android?

OpenCode itself is free and MIT-licensed. On Termux + proot the software is free and your only cost is provider tokens. On Cosyra you pay for the cloud workspace. OpenCode there starts on Big Pickle, a free OpenCode Zen model with a daily message limit. For more, run /connect and pay that provider directly. We do not proxy or meter your model calls.

tl;dr

Three real ways to run OpenCode from an Android phone as of 2026-07-16. Cosyra (native Android app, OpenCode pre-installed in a persistent Ubuntu 24.04 x86_64 container, no arch misdetection, nothing to babysit). Termux + proot-distro (free, on-device, because plain Termux misdetects the arch per issue #21043 and PR #21106 was closed without merging). SSH from Termux into your own always-on box. OpenCode is the one agent of the four where plain Termux still breaks. Claude Code and Gemini CLI do not.

Google Play / App Store. Sign up and pick a plan, from $20/month.

Run OpenCode on your Android phone in three minutes. Install Cosyra, tap the OpenCode shortcut and send your first prompt.

See pricing