Run GitHub Copilot CLI on Your Phone (iPhone + Android)

GitHub Copilot CLI runs on macOS, Linux, and Windows — there is no iPhone or Android build, and it fails to install in Termux. So to run it from a phone you put it on a real Linux machine and reach it. The fastest way: install Cosyra for iOS or Cosyra for Android, then npm install -g @github/copilot in the terminal — Node 22+ is already there — authenticate with a token, and run copilot. GitHub also has a mobile feature, but it only remote-controls a session running on your own desktop. Here is each path.

This guide was written by the Cosyra team. We checked every moving part against primary sources, the remote-control GA re-verified 2026-06-30: the github/copilot-cli repo, GitHub's Copilot CLI docs and changelog, the npm package, and the open Termux tracking issues #1257 and #3333. Versions and dates below carry that date.

What is GitHub Copilot CLI?

GitHub Copilot CLI is GitHub's agentic coding tool for the terminal. It is not the old gh copilot extension that suggested shell commands — it is a full agent that reads your repo, edits files, runs commands, and builds and tests, with a plan mode and an autopilot mode and support for MCP servers and custom agents. It ships as the npm package @github/copilot and launches with the copilot command.

• Timeline: public preview 2025-09-25, general availability 2026-02-25 (version 1.0.65 as of 2026-06-24).
• Platforms: macOS, Linux, and Windows, plus GitHub Codespaces. No native iOS or Android build exists.
• Prerequisite: Node.js 22 or later — see running Node.js on your phone for why that matters on mobile.
• Safety: GitHub's docs state Copilot will not change your files without explicit approval, and you confirm you trust the working directory first.

Because it is a Node binary that expects a real shell, it has the same mobile problem as every other coding CLI: the phone is the wrong place to run the process. The trick is putting the process somewhere real.

The official "Copilot on mobile" is remote control, not the CLI

This is the part that trips people up. After an April 2026 public preview, GitHub made remote control generally available on 2026-05-18: you "monitor and steer a running CLI session" from the GitHub web app, GitHub Mobile (iPhone, iPad, Android), VS Code, or JetBrains. You press a shortcut in the CLI, scan a QR code, and drive the session from your phone. GA also added support for non-GitHub repositories and standalone directories. It is real and it is handy — but GitHub is explicit about the architecture: the CLI runs on your local machine or workstation, while the mobile device functions as a remote control and monitor.

So the phone is a window onto a session running on a desktop you left awake. The machine has to stay awake and online for the remote interface to work; if it sleeps or drops its connection, remote control is unavailable until it is back, and GitHub ships a /keep-alive command to stop the box from sleeping mid-run. If you have a desktop you can keep powered on, that fits. If you do not have a Mac or PC sitting powered-on at home, it does not help — and that is exactly the gap a cloud container fills. This same remote-control-versus-cloud-container split shows up across every agent; we map both paradigms in AI pair programming from a phone.

How can you run Copilot CLI from a phone?

Three ways, in order of how well they work without a desktop: a cloud Ubuntu container where Copilot CLI actually runs (Cosyra), GitHub's remote control of a desktop session, and Termux on Android (which does not currently install).

1. Cosyra: install Copilot CLI in a cloud container

Cosyra is a native iOS and Android terminal connected to a persistent Ubuntu 24.04 container. It ships Node 22+, so npm install -g @github/copilot works, and the CLI runs in the container — nothing of yours has to stay awake.

• Works when: you want Copilot CLI running on demand from either platform with no home machine to maintain.
• Breaks when: you have no internet, or you specifically need it reaching resources only on your desktop's local network.
• Cost: 1 hour free on signup, no credit card; a 10-hour, 7-day trial; then $29.99/month or $300/year. See pricing. You pay GitHub for Copilot separately.

2. GitHub remote control of a desktop session

The GA feature above (generally available 2026-05-18). Best when you already run Copilot on a desktop and just want to keep an eye on it or nudge it from the couch — from GitHub Mobile, the web, VS Code, or JetBrains. Needs that desktop awake, with /keep-alive to stop it sleeping.

3. Termux on Android — why it fails today

Copilot CLI does not install cleanly in Termux. It bundles a native pseudo-terminal module, pty.node, and there is no Android arm64 prebuild, so the install fails:

A GitHub tracking issue for Termux/Android support (#1257) is open and has no committed fix; unofficial community scripts try to build the native deps by hand. And it got harder, not easier: as of v1.0.48+ the CLI added a second native module, runtime.node (a Rust addon that handles token counting, MCP config parsing, hooks, and session state), compiled against glibc. Termux's Node is built on Android's Bionic libc, and you cannot mix glibc and Bionic in one process, so even a patched pty.node hits a second wall (#3333, open since 2026-05-15; people are pinning to v1.0.45 to dodge it). Even past both, Android 12+ can kill long-running processes — the same issue we cover in Cosyra vs Termux. A cloud x86_64 container sidesteps the whole class of problem.

How do you run Copilot CLI on iPhone or Android with Cosyra?

Four steps: install the app, install @github/copilot, authenticate with a token, and run copilot in a repo.

Step 1: Install Cosyra and sign in

Download from the App Store or Google Play. The container ships a current Node LTS (Node 22+), which is Copilot CLI's prerequisite.

Step 2: Install GitHub Copilot CLI

Copilot CLI is not one of the four agents we pre-install, but it is one command away because Node is already set up.

Step 3: Authenticate with a token

For a container, GitHub recommends a token over interactive login. Create a fine-grained personal access token with the Copilot Requests permission, export it, and Copilot picks it up. (Interactively, you can instead run /login inside the CLI.)

GitHub documents this token path as the recommended approach for containers and non-interactive environments. The precedence, if more than one is set, is COPILOT_GITHUB_TOKEN, then GH_TOKEN, then GITHUB_TOKEN.

Step 4: Clone a repo and run Copilot

Copilot proposes the edits and waits for your approval before writing. You see the diff on the phone before anything lands on disk — and the persistent container means you can pick the session back up on an iPad later.

What are the real limits of running Copilot CLI on a phone?

• No offline mode. The container is in the cloud; no internet, no terminal.
• A paid Copilot plan is required. GitHub's GA announcement lists the CLI under Pro, Pro+, Business, and Enterprise. That bill is separate from the environment you run it in.
• Phone keyboards slow long prompts. Voice dictation and a Bluetooth keyboard help a lot.
• Autopilot mode is powerful — be deliberate. Copilot can run without per-step approval; on a phone, where one mis-tap approves a lot, keep it on the approval path unless you are watching closely.

Cosyra vs GitHub remote control vs Termux for Copilot CLI

Cosyra runs the CLI for real with nothing left awake; GitHub's remote control is great if a desktop is already running the session; Termux does not install today. The table lines them up, verified 2026-06-28.

Want the full head-to-head on pricing, platforms, and where each tool wins? Our Cosyra vs GitHub Copilot CLI comparison lines them up row by row.

Prefer one of the agents that is pre-installed? See Claude Code on phone, Codex CLI on phone, Gemini CLI on phone, and OpenCode on phone, or the pillar on AI coding agents on mobile. To use any of them for reviewing code, see reviewing pull requests from your phone.

Frequently asked questions