Android CLI is a command-line tool "that lets you build for Android more efficiently using any tool of your choice," in Google's own description of the tool. It standardizes the entry point to Google's official tools, skills, and documentation, so an agent (or a script) can do real Android work without ever opening Android Studio. Worth separating early from a namesake: github.com/sedbytes/android-cli is an unrelated third-party project that happens to share the name. The one this article covers is Google's, and its docs carry a "last updated" stamp of September 25, 2026, with three separate release notes landing that same month.
What is Android CLI?
The overview page also frames it as an automation layer for CI pipelines: "It can also streamline CI, maintenance, and any other scripted automation for the increasingly distributed nature of Android development." For a team, that's the practical shift. An agent can now run create, run, emulator start, and screen capture from a terminal or a CI job, the same commands a developer would type by hand, with no IDE process required to back them.
Where it fits next to sdkmanager, avdmanager, and adb
In practice, android sdk install covers ground sdkmanager used to own, and android emulator overlaps with avdmanager. Device-inspection commands like screen capture and layout dumping land on ground adb has covered for years. None of that forces a team off adb or sdkmanager. It gives an agent one consistent tool to call instead of three, each with its own flag conventions.
What commands does Android CLI include?
The full command set spans project setup, device control, SDK management, documentation lookup, a bridge into Android Studio, and skills. Grouped:
| Group | Commands | What it does |
|---|---|---|
| Project | create, run, install | Scaffolds, builds, runs, and installs a project |
| Device | emulator create/list/remove/start/stop, screen capture/resolve, layout | Manages emulators, captures on-screen state, dumps layout hierarchy |
| SDK | sdk install/list/remove/update | Installs, lists, removes, and updates SDK packages |
| Docs | docs search/fetch | Searches and pulls official Android documentation |
| Studio bridge | studio analyze-file, studio find-usages, studio render-compose-preview (plus check, find-declaration, open-file, version-lookup) | Reaches a running Android Studio instance for its own inspections, symbol lookups, and Compose preview rendering |
| Skills | skills add/find/list/remove/update | Installs, discovers, lists, removes, and updates shared agent instructions |
Beyond those, a handful of housekeeping commands round things out: init, describe, info, update, help, and completion.
What are Android skills, and how do agents use them?
The android-skills overview defines them plainly: "Android skills are AI-optimized instructions, to help AI tools and agents better understand and execute specific patterns that follow best practices and guidance on Android development." They live in the Android skills GitHub repository, and the reasoning behind keeping them separate from the model itself is a context-window problem: "Skills represent on-demand expertise. This structure lets the agent maintain a large number of specialized capabilities without cluttering the model's immediate context window." A model decides on its own when a request matches a skill's description, then pulls in the full instructions only at that point.
That's a meaningful change for a team, separate from the tool that runs the commands. A skill for migrating XML layouts to Compose, upgrading to AGP 9, or auditing an R8 configuration becomes a shared, versioned document your team maintains once, rather than something each engineer re-explains to their own agent in a private prompt. Android skills also follow the open agent skills standard, so they work with any AI tool that supports skills, including tools outside Google's own lineup.
Handing an agent run, emulator start, and skills add inside a real project is handing it working capability, and that's exactly the kind of decision HighCircl's AI in the engineering workflow: tools, permissions and policy hub tracks across other tools.
How does the skills command work?
skills list shows what's available. skills add skill-name installs one, and running it again on a skill you already have updates it to the latest version. skills find and skills remove cover discovery and removal, and a dedicated skills update command shipped in September 2026 for updating without re-adding.
How to add an Android skill
1. List available skills
Run android skills list to see what's available before installing anything.
2. Install a skill
Run android skills add skill-name, swapping in the skill's actual name from the list. The agent picks up the skill's full instructions the next time a request matches it.
3. Update it later
Run android skills add skill-name again and it updates to the latest version automatically. A dedicated android skills update command does the same job without needing the name.
How does Android CLI connect to a running Android Studio instance?
The studio subcommand is where Android CLI stops being a standalone tool and starts talking to the IDE. Google's May 2026 stable 1.0 announcement describes the new studio command as giving an agent access to Android Studio's own deep, contextual code analysis and preview tools from the command line: analyze-file runs the editor's own inspections, find-usages finds references to a symbol, and render-compose-preview renders a Compose UI preview, all without a human clicking through the IDE. The same release added Journeys, natural-language descriptions of user flows an agent can turn into runnable tests, and made Android CLI installable through apt-get, winget, and homebrew.
This ties directly into a workflow HighCircl already covers from the other direction. Android Studio's Bring Your Own Agent plugs an external agent into the IDE itself, giving it the project graph, Compose previews, and shell access from inside Studio. Android CLI's studio bridge does the opposite: an agent working from a terminal or CI job reaches into Studio's inspections and preview renderer without the IDE being where the agent lives. Same capabilities, opposite starting point.
Android CLI's own workflow suggestion in Google's April 2026 launch post is to start a prototype quickly with an agent using the CLI, then open the same project in Android Studio to fine-tune the UI by hand. That pairing is also where Google's Antigravity bundles in: the stable 1.0 release notes that Google Antigravity now includes an optional bundle of Android resources, Android CLI and skills among them.
Android CLI is the tool that gives an agent terminal access to an Android project in the first place. Whether an agent does good work once it has that access is a separate, measurable question, and it's the one Android Bench 2.0 is built to answer, not this tool.
What's new in the latest Android CLI release?
The release notes page tracks a fast release cadence since launch:
| Version | Date | What changed |
|---|---|---|
| 0.7 | April 2026 | First release |
| 1.0.15433482 | May 2026 | studio command added, Journeys support |
| 1.0.15857036 | July 2026 | Agent skills support, native downloader with proxy support |
| 1.0.15985488 | July 2026 | Dedicated install command, cross-platform SDK management |
| 1.0.16251017 / 1.0.16261425 | September 2026 | Layout dump, shell completion, skills update, layout fixes |
| 1.0.16406183 | September 2026 (current) | Faster startup, non-zero exit codes on failure, --headless emulator, --application-id/--namespace/--min-sdk flags on create |
The current release also fixed a layout command issue on older API levels, and the faster startup comes from loading the native downloader library only when it's actually used, instead of unpacking it on every invocation.
The 70% token figure and 3x speed claim attached to Android CLI both come from that same April 2026 launch post, which reports that the tool "improved project and environment setup by reducing LLM token usage by more than 70%" and that agent-driven tasks finished three times faster than when agents worked through the same tasks using only the standard toolsets. Those are Google's launch numbers, not independently measured figures, and they describe project setup and tooling tasks specifically rather than every command in the tool.
FAQ
What is Android CLI?
A command-line tool from Google for building Android apps outside Android Studio, covering project setup, emulator and SDK management, documentation lookup, a bridge into a running Studio instance, and agent skills. It's built for both interactive use and CI.
What are Android skills?
Markdown-based instruction sets (SKILL.md files) that give an agent specialized, on-demand guidance for a specific task, like migrating XML layouts to Compose or upgrading to AGP 9. They live in a public GitHub repository and follow an open standard, so they work with any AI tool that supports skills.
Does Android CLI replace Android Studio?
No. It runs alongside Studio for terminal and CI work. The studio subcommand reaches into a running Studio instance for its own inspections and Compose preview rendering, and a project started with Android CLI opens normally in Studio whenever you want its editors and debugger.
How do I install an Android skill?
Run android skills list to see what's available, then android skills add skill-name to install one. Running that same command again later updates it to the latest version, or use the dedicated android skills update command.
How do I install Android CLI itself?
Google's stable 1.0 announcement lists apt-get, winget, and homebrew as supported package managers, so installation follows whichever one already fits your platform.