OpenCode on iPhone: 3 Ways to Run It

You can run OpenCode on iPhone today, but not on the phone itself. OpenCode ships prebuilt binaries for macOS, Linux, and Windows, and iOS gives you none of those — there is no Termux for iPhone, and the local terminals that do exist cannot run a modern Node.js. So on an iPhone the agent always runs on a host elsewhere and your phone drives it. The fastest path is Cosyra on the App Store: a cloud Ubuntu 24.04 container with OpenCode pre-installed that you reach from a native iOS app. Connect a provider, type opencode, and you are in the TUI. Sign up gets you 1 hour free, no credit card. The two other real paths are SSH from Blink Shell into your own Linux box, and OpenCode's own opencode serve headless server reached over a private network.

This is the iPhone-specific companion to our OpenCode on your phone walkthrough, which covers iPhone and Android together. The iPhone earns its own page because iOS changes the answer in one big way: Android has Termux, so on a Pixel or Galaxy you can fall back to a proot-distro chroot to get closer to the metal (we cover that in OpenCode on Android). iOS has no equivalent. That single difference is why the iPhone story is all about reaching a host, never about running OpenCode on the device. If you want the bigger tablet form factor, see OpenCode on iPad; for the full picture of every agent on mobile, start at our AI coding agents on mobile pillar.

Why won't OpenCode run locally on an iPhone?

OpenCode will not run locally on an iPhone because iOS has no Linux userland and the on-device terminals cannot run a modern Node.js. OpenCode is distributed as a Node package (opencode-ai) plus a platform-matched prebuilt binary, and the README lists its targets as macOS, Linux, and Windows. iOS is not one of them, and Apple does not allow a Termux-style app that ships a general-purpose Linux environment with a package manager. So the two well-known iOS terminals each hit a wall:

• iSH emulates 32-bit i386 Alpine Linux. Modern Node.js crashes with Illegal instruction under that emulation — tracked in iSH issue #2335, open since 2024-01-21 — and the i386-only target rules out OpenCode's prebuilt binaries anyway. No working Node means no OpenCode.
• a-Shell ships native iOS-compiled tools and a curated set of WebAssembly binaries. It is genuinely useful, but it has no apt, no apk, and no global npm install path, so there is nowhere to put OpenCode.

Here is an opinion the "just self-host it" crowd pushes back on: keeping a machine awake at home so your phone has something to talk to is the exact chore that mobile coding is supposed to remove. OpenCode's opencode serve is a genuinely good design, and we link the docs below, but a server you babysit is still a server you babysit. When the home box sleeps on the train, the phone has nothing. We pre-install OpenCode in a cloud container precisely so there is no second computer in the loop. For the local-terminal limits in more depth see Termux for iPhone and Cosyra vs iSH.

What are the three ways to run OpenCode on iPhone?

There are three real ways to run OpenCode from an iPhone as of 2026-06-30: a cloud terminal with OpenCode pre-installed (Cosyra, native iOS app), SSH from a terminal app into your own always-on Linux box, or OpenCode's own headless opencode serve on a machine you own, reached over a private network. All three share the same shape: the agent runs on a host and the iPhone is the remote. They differ in who owns and babysits that host.

1. Cosyra (cloud terminal, native iOS app)

This is what we build. The Cosyra iOS app gives you a persistent Ubuntu 24.04 container with OpenCode, Claude Code, Codex CLI, and Gemini CLI already installed, 30 GB of storage, and hibernation that resumes exactly where you left off. We pre-install the four agents because setup friction is the thing that actually kills agent-driven mobile coding; nobody wants to debug a curl installer or a Node version on a phone keyboard. There is no SSH tunnel to keep alive and no laptop that has to stay awake. The same container is reachable from iPhone, Android, and web, so you can start on the couch and pick it up in a waiting room.

• Works when: you want zero setup and a host you do not have to maintain, and you want the real OpenCode TUI rather than a remote view of it.
• Breaks when: you have no internet — the container lives in the cloud, so there is no offline mode. That is a real trade-off against a local terminal.
• Cost: 1 hour free on signup, no credit card. Extend with a 10-hour, 7-day trial when you want more. After that, $29.99/month or $300/year. OpenCode is free and MIT-licensed; you bring your own model-provider key and pay the provider directly. See pricing.

2. SSH from Blink Shell into your own machine

The classic remote-into-your-own-box path. Blink Shell is a paid iOS terminal built around SSH and Mosh. Mosh matters on a phone: it keeps the session alive across the cellular handoffs and IP changes that drop plain SSH the moment you walk between cell towers. You SSH into a Linux box or VPS where you installed OpenCode with npm i -g opencode-ai@latest or the curl -fsSL https://opencode.ai/install | bash script, start tmux so the TUI survives app switching, and drive it from there.

• Works when: you already keep an always-on machine and are comfortable with SSH plus tmux.
• Breaks when: the machine sleeps, the home connection drops, or you do not want to keep a second computer awake just to give the phone a target.
• Cost: the Blink+ subscription plus whatever the host costs. Tailscale's free tier covers the personal networking.

3. opencode serve / opencode web on your own host

This is OpenCode's own remote-friendly design, and it is the one genuinely distinctive path here. opencode serve runs a headless HTTP server (default port 4096, default hostname 127.0.0.1), and opencode web starts a browser UI you can open in Safari. Because the default binds to localhost, the safe way to reach it from a phone is over a private network rather than the public internet: put the host on a Tailscale tailnet, run the server, and set OPENCODE_SERVER_PASSWORD so it is not wide open. Then the iPhone hits the web UI or the API directly.

• Works when: you run a free, open-source agent on hardware you control and are comfortable with the networking setup.
• Breaks when: the host sleeps, or you do not want to expose and secure a server just so the phone has a target. The default localhost bind means anything wider is your responsibility to lock down.
• Cost: free software (MIT) plus the host and your model-provider tokens. This is the cheapest path if you already run an always-on box.

How do you set up OpenCode on iPhone with Cosyra?

You set up OpenCode on iPhone in about three minutes: install Cosyra from the App Store, connect a model provider inside the container, and type opencode. No Node install, no SSH tunnel, no jailbreak. These are the exact steps we run on a fresh iPhone.

Step 1: Install Cosyra on iPhone

Open the App Store on your iPhone and search for Cosyra. Sign in with Apple, Google, or email and the app provisions a fresh Ubuntu container on first launch, about 15 seconds in our testing. The four agent CLIs are already inside, so you skip the part that breaks most on-phone setups.

Step 2: Connect a model provider

OpenCode is provider-agnostic, so the one setup step is authenticating a backend. Start opencode and connect Anthropic, OpenAI, Google, or a local model:

The credentials persist with the container's home volume, so you connect once and they are there next time. OpenCode itself is free; the provider bills you for tokens.

Step 3: Clone a repo and run opencode

Clone a repo and start the TUI:

OpenCode reads the repo and starts working. The two built-in agents matter on a phone: build has edit access for changes, and plan is read-only for when you just want analysis without the agent touching files. When you close the app to catch your stop, the container hibernates; reopen it and the session is exactly where you left it, with no re-clone and no re-auth.

What does iPhone OpenCode look like in practice?

iPhone OpenCode in practice is short prompts, one hand, and dead time that used to be wasted. The phone is not where you do a four-hour refactor; it is where you keep a long task moving while you are away from the desk. Two patterns we run constantly:

The commute kickoff

Standing on the platform, you remember the failing CI job from last night. Open Cosyra, pull the branch, and hand OpenCode the whole problem in one dictated sentence — press and hold the mic key, say it, release:

By the time the train arrives you have a diff to skim. Because OpenCode is provider-agnostic, you can switch the model on the fly with --model if the cheap model stalls on the hard part — useful when you are watching token spend on a personal key.

The waiting-room review

Fifteen minutes in a waiting room is enough to review a teammate's pull request. Pull the branch, drop into OpenCode's plan agent so it reads without editing, ask for a structured review of what you care about, and post it with gh pr review --comment from the same terminal. The container holds your gh auth, so there is no login dance. This is the kind of work the phone is genuinely good at: bounded, reviewable, no deep window juggling required. We think the on-screen keyboard is fine for this — the work is prompts and approvals, not hand-typing functions, and most people who say otherwise have not tried it on a real commute.

How do the iPhone options compare?

The three paths line up cleanly against what matters for an agent client: whether you maintain the host, whether you get the real CLI, and what happens when you switch apps or lose signal. The table covers the real options as of 2026-06-30. For the wider field of editors and terminals beyond OpenCode, our coding on iPhone guide lines every option up the same way, and best terminal apps for iPhone covers the client side.

Which path should you pick?

Choose Cosyra if you want the real OpenCode TUI with no host to maintain and the same container across iPhone, Android, and web — and the other three agents next to it. Choose Blink plus SSH if your dev box is already always-on and Linux, and you want OpenCode running on hardware you control. Choose opencode serve if you want to lean into OpenCode's open-source, self-hosted design for free and do not mind the networking setup. It is the honest pick for anyone who values MIT-licensed software on their own box over convenience. The one combination iOS cannot give you is OpenCode running on the phone itself; on Android the calculus shifts because Termux gets you closer to local, which is the whole point of our OpenCode on Android guide.

Frequently asked questions