Gemini CLI on Android: 3 Real Ways to Run It

You can run Gemini CLI on Android, but not as an app you install from the Play Store. Google's Gemini CLI is the @google/gemini-cli Node.js binary, and as of 2026-06-25 it ships for macOS, Linux, and Windows only. Two things also changed in mid-2026 that most blog posts miss: the free personal-account login ended on 2026-06-18, so you now need a paid API key wherever you run it, and recent versions fail to build on Termux because of Android NDK dependencies. So "Gemini CLI on Android" means one of three real paths: a cloud Ubuntu container with the CLI pre-installed (Cosyra on Google Play, where you type gemini, 1 hour free, no credit card), Termux on-device with workarounds, or SSH into your own Linux box. This guide walks each one honestly.

This is the Android-specific companion to our Gemini CLI on your phone walkthrough, which covers iPhone and Android generically; if you reach for a tablet with an external keyboard, the Gemini CLI on iPad guide is the device-specific companion. What changes on Android is that Termux is a real on-device option, unlike on iOS, but the Gemini CLI story there runs through build workarounds and community forks rather than a clean install, which is the part most guides get wrong. The sibling agents have the same shape: see Claude Code on Android and Codex CLI on Android, and for the full map of what the OS can run as a dev environment, our Coding on Android pillar. If you want to understand the Termux-and-proot route in depth, the Linux container on Android guide covers it. For the broader picture across all four mobile AI agents, see AI coding agents on mobile.

Why is there no native Gemini CLI on Android?

There is no native Gemini CLI on Android because Google does not ship one. The google-gemini/gemini-cli README describes "an open-source AI agent that brings the power of Gemini directly into your terminal," distributed through npm, Homebrew, and MacPorts for macOS, Linux, and Windows. It is an Apache-2.0 Node.js binary that needs Node 20 or newer. Android is not a target.

Android phones run an arm64 Linux kernel, so on paper Termux should be able to run a Node CLI. In practice the install breaks on recent versions. Native dependencies such as tree-sitter-bash expect an Android NDK toolchain Termux does not fully provide, which shows up as build failures on arm64 (issue #11254, 0.11.0-nightly on Node v24) and earlier install failures (issue #7895, 0.3.3 on Node v22.19.0). There is also a clipboardy bug that mis-detects Termux and refuses to run with a false "You need to install Termux" error, which Google closed as "not planned" (issue #13784). On x86_64 Ubuntu with glibc, these native modules build normally, which is the whole reason a cloud container is the least brittle option.

What changed on 2026-06-18 (the free login is gone)

The headline reason people ran Gemini CLI used to be the free personal-account login: sign in with a Google account and get 60 requests per minute and 1,000 per day at no charge. That path stopped serving requests on 2026-06-18 as part of Google's transition to Antigravity CLI; the free OAuth endpoint now returns HTTP 410 Gone (Google Developers Blog). The open-source gemini binary still works, but only with a paid GEMINI_API_KEY from Google AI Studio or Vertex AI. Google's successor is Antigravity CLI (binary name agy, a closed-source Go rewrite), which did not ship at feature parity and has no published free-request quota.

We have an opinion the local-tooling crowd will push back on: running Gemini CLI on-device on Android is a trap in mid-2026. You fight an NDK build, pin an old version or run a fork, accept that Android can SIGKILL your session, and at the end of all that you still need a paid key, because the local-and-free pitch quietly stopped being true on 2026-06-18. If you are paying for the key anyway, paying for a Linux box that actually builds the CLI is the smaller hassle. On a Pixel on the couch, that is the difference between coding and debugging a toolchain.

What are the three real ways to run Gemini CLI on Android?

There are three real ways to run Gemini CLI from an Android phone as of 2026-06-25: Cosyra (cloud container with the CLI pre-installed on x86_64), Termux with build workarounds (on-device, free shell), and SSH into your own always-on Linux box. We walk each below.

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, or foldable. Gemini CLI is pre-installed on Node 20 alongside Claude Code, Codex CLI, and OpenCode, and because the image is glibc x86_64, the tree-sitter-bash and clipboardy failures that plague Termux simply never appear. You get 30 GB of persistent storage, session hibernation that resumes exactly where you left off, and the same container reachable from iPhone, iPad, and a browser. BYOK applies: you paste a paid GEMINI_API_KEY and Google bills you directly. We do not proxy or meter your model calls.

• Works when: you want a current Gemini CLI with zero setup, full x86_64 Ubuntu compatibility, and the same environment across every device you pick up.
• Breaks when: you have no internet. The container lives in the cloud, so there is no offline mode. That is a genuine trade-off versus a local Termux install.
• Cost: Sign up — 1 hour free, no credit card. Extend with a 10-hour, 7-day trial when you want more. After that, $29.99/month or $300/year. See pricing.

2. Termux (on-device, free shell)

Termux is an open-source (GPLv3) Android terminal emulator with a real package manager. The Linux shell is genuinely free and offline-capable, which is its honest advantage. Getting Gemini CLI running inside it is the hard part. A bare npm install -g @google/gemini-cli trips the native-build and clipboardy failures above, so the working recipes are: install with --ignore-scripts to skip the failing native step, pin an older release with @google/gemini-cli@0.2.2, or use the community DioNanos/gemini-cli-termux fork that is maintained for Termux. All three trail the upstream release.

• Works when: you want a free, local shell on Android, you are comfortable maintaining a workaround or a fork, and you accept that it lags the official release.
• Breaks when: an upstream change outpaces the fork, the pinned version misses a feature you want, or you hit the Android 12+ phantom-process killer on a long session (the same signal 9 issue we document in the Claude Code on Android guide). You also still need a paid API key.
• Cost: free shell, paid API key.

3. SSH into your own always-on Linux box

The classic remote route still works. Run Gemini CLI on a Linux machine you own, a home server, a VPS, or a desktop you leave on, where its native dependencies build cleanly, and reach it from a phone SSH client. Termux doubles as a capable SSH client, or you can use a dedicated app. The phone is just the terminal; the agent runs on the host. The catch is that the host must stay awake and reachable, and you maintain it yourself, which is the chore a managed container removes. If you go this way, pairing it with a mesh VPN keeps the box reachable without exposing a public SSH port.

How do you run Gemini CLI on Android with Cosyra?

You set up Gemini CLI on Android in about three minutes: install Cosyra from Google Play, paste a paid API key into the Ubuntu container where Gemini CLI is already installed, and type gemini. The steps below are exactly what we run on a fresh Pixel.

Step 1: Install Cosyra from Google Play

Open the Google Play Store and install Cosyra. The Android app runs on Pixel, Samsung Galaxy S and Z foldables, OnePlus, Nothing, and any device on Android 9 or later. Sign in with Google, Apple, or email and the app provisions a fresh Ubuntu 24.04 container with Gemini CLI, Claude Code, Codex CLI, and OpenCode already installed.

Step 2: Paste a paid Gemini API key

Create a key at Google AI Studio (or use a Vertex AI key). Since the free personal-account login ended 2026-06-18, a paid key is required. In the Cosyra terminal:

Step 3: Clone a repo and run gemini

Gemini reads the repo and starts working. When the screen locks the container keeps running; reopen the app and the session is exactly where you left it. The phone keyboard is fine for the natural-language turns, because you are writing one sentence of intent at a time, not 40-line functions. Most people who say mobile coding is impossible have not actually tried it on a commute.

How do the Android options compare?

The three paths line up against what matters for running an agent from a phone: whether it installs cleanly, whether it stays on the current version, whether it needs another machine, and whether the shell works offline. The table covers the state as of 2026-06-25.

Choose Cosyra if you want a current Gemini CLI with nothing to babysit and the same container across Android, iPhone, iPad, and web. Choose Termux if a free, local, offline shell matters more than running the latest version and you do not mind maintaining a workaround. Choose SSH if you already keep a Linux 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.

Frequently asked questions