Goose on Android: No Play Store App for Block's Agent

There is no Goose Android app on the Play Store as of 2026-06-10. If you searched block goose android expecting Block's AI agent on Google Play, here is the honest picture: goose left Block for the Linux Foundation, and its only mobile client is an iOS remote control with no Android version shipped yet. The way to actually run goose on Android today is to install the open-source goose CLI inside a cloud Linux container and reach it from a native app: install Cosyra for Android, run curl -fsSL .../download_cli.sh | bash, then goose configure and goose session. 1 hour free on signup, no credit card.

This guide was written by the Cosyra team. We installed and ran goose inside a Cosyra container from an Android phone, and we cross-checked every claim against the official aaif-goose/goose repo, the goose-mobile README, and the work-in-progress Android port, verified 2026-06-10.

Is there a Goose Android app?

No official one. We searched the Play Store for goose on 2026-06-10 and found no shipped app from the goose project. Three things exist, and it helps to name each so you do not download the wrong one:

• A work-in-progress port. michaelneale/goose-android is an early Android client, described in its own repo as based on goose-ios. It had about 20 stars and was last pushed 2025-12-16 when we checked: not a Play Store release, and not actively shipping.
• A device-automation proof of concept. The goose-android-agent directory in the goose-mobile repo is an experimental agent that automates your whole Android device. Its own README says it needs deep device access and is best considered experimental. It is not the goose coding agent.
• An official "planned" note. The goose-mobile README says an Android client is planned as a port of the iOS remote control and "will be available on google play store eventually." Eventually is not today.

So if your plan was "download the Goose app on my Pixel and start coding on the bus," there is no app to download. That is not a knock on the project; goose is a serious open-source agent, and this is just the honest state of the Android client.

Wait, isn't goose a Block product?

It started at Block, which is exactly why "block goose android" is a common search. The naming is now out of date. goose moved to the Agentic AI Foundation under the Linux Foundation, and the repo lives at aaif-goose/goose, about 48,600 stars, Apache-2.0, latest release v1.37.0 (2026-06-03) as of 2026-06-10. The accurate phrasing is "originally built at Block, now a neutral Linux Foundation project." If you were looking for a Block-published app on Google Play under that old branding, it does not exist, and it would not be published by Block today anyway.

Can you run goose on Android with Termux?

This is the first thing most Android developers try, and it is more friction than it looks. The official installer pulls a prebuilt binary built against glibc. Termux runs an Android bionic-libc userland, so that binary will not just execute, so you would reach for proot-distro to put a real Linux userland on top, then install goose inside that. It is doable, but it is a stack of moving parts, and the agent stops the moment Android kills the background process or the battery dies on a long task.

The opinion we hold that the self-host crowd will disagree with: for an autonomous agent that you want to keep working while your phone is in your pocket, a cloud x86_64 box beats a phone-local userland. The same one-line installer that fights Termux pulls a binary that runs immediately in a container, and the agent keeps going while the phone sleeps. If you genuinely need offline, Termux is the only thing that runs with no signal, and we say so plainly in Cosyra vs Termux. For the goose-specific version of this argument — self-hosted local agent plus iOS remote versus a hosted cloud container, and what the "free" stack really costs — see Cosyra vs goose.

How to run goose on Android via a cloud container

The setup is about five minutes. It is the same install whether you are on a phone or an Android tablet, because the work happens in the container, not on the device. For the cross-platform version of this walkthrough, including the iOS paths, see Run goose on your phone.

Step 1: Install the Cosyra Android app

Install from Google Play and sign in with Google, email, or Apple. On first launch we provision a fresh Ubuntu 24.04 container with Node.js, Python, Git, and tmux already on it. This is the always-on machine goose runs on — the thing the iOS remote app makes you supply yourself.

Step 2: Install the goose CLI

One command. Because the container is x86_64, the installer pulls a prebuilt binary — a download, not a build, and not the libc fight you get in Termux. We ran this in a fresh container and goose --version reported 1.37.0.

Step 3: Configure your LLM provider

goose is BYOK and model-agnostic. Run goose configure, pick a provider, and paste your own key. The config lands in the container's home volume, so it survives hibernation and is there the next time you open the Android app.

Step 4: Start a goose session

Clone your repo, cd in, and start a session. Describe the change; goose plans, edits, runs commands, and tests, then reports back. Lock the phone mid-task and the work continues in the cloud.

Who should wait for the official app, and who should not?

Wait for the official Android client if you specifically want goose's own remote-control app and you already run a powerful machine at home around the clock to point it at — that is the shape the iOS app and the planned Android port are built for, and it is free. Use a cloud container now if you do not want to own, power, and patch a home server, if you want the agent to keep running while your phone is locked, or if you want goose sitting next to Claude Code, Codex CLI, OpenCode, and Gemini CLI in one persistent Linux workspace.

The honest tie-breaker: a remote-control app, whenever the Android version ships, still needs a machine you keep on somewhere. The cloud container is that machine, already on, reachable from the native Android app with no tunnel to configure. For the broader map of agent CLIs on a phone, see the AI coding agents on mobile pillar.

Frequently asked questions