Android CLI and Skills: Google Makes Android Development 3x Faster With Any AI Agent

On April 16th, Google published an announcement on the [official Android Developers blog]](https://android-developers.googleblog.com/2026/04/build-android-apps-3x-faster-using-any-agent.html) that took less than a week to become the conversation: Android CLI, a new front of tooling designed from the ground up for AI agent workflows. I found out about it through this tweet from AristiDevs, and after going through it in detail, I think it deserves a proper look. It is not the first time Google makes a strong move on the Android side: I wrote about something similar not long ago with the resizing changes in Android 16.

What is actually on the table

The announcement is not a single tool, but three pieces that complement each other.

1. Android CLI

A terminal interface for the entire Android development cycle: installing the SDK with only what you need (android sdk install), creating projects from official templates with the recommended architecture already wired up (android create), managing emulators (android emulator) and deploying (android run). And, as you would expect in 2026, it updates itself with android update.

The interesting number comes from Google’s internal experiments: compared to the classic stack, the new Android CLI cuts LLM token usage by more than 70% and completes tasks 3 times faster. Fewer tokens means a lower cost per interaction, something anyone working with agents seriously will appreciate on the invoice at the end of the month.

2. Android Skills

A public GitHub repository with modular “skills” written in Markdown (SKILL.md) that agents invoke automatically when the user’s prompt matches the skill’s metadata. The first batch already includes things as concrete as:

• Navigation 3 setup and migration.
• Edge-to-edge implementation.
• AGP 9 and XML to Compose migrations.
• R8 analysis and configuration.

You can browse them with android skills from the CLI itself.

3. Android Knowledge Base

Available through android docs and also integrated into Android Studio, it lets agents search and pull authoritative, up-to-date documentation (the official Android, Firebase, Google Developers and Kotlin guides) regardless of your model’s cutoff. In practice: no more hallucinations about APIs that changed two versions ago.

The best part: it is not Gemini only

Google is explicit about it in the announcement:

“Whether you are using Gemini in Android Studio, Gemini CLI, Antigravity, or third-party agents like Claude Code or Codex…”

In other words, Claude Code and Codex are first-class citizens in this ecosystem. That a platform as big as Android embraces third-party agents instead of walling itself into its own garden is, to me, the best news in the whole announcement.

Why Android CLI matters

Until now, using an agent to write Android code meant fighting three things at once: tokens wasted reading enormous file trees, outdated dependencies sitting in the model’s memory, and not enough context for architectural decisions. Android CLI, Skills and the Knowledge Base go after all three, and they do it without tying you to one specific agent.

If you work with Claude Code or Gemini CLI and you build Android apps (or you are thinking about starting), this changes the cost and speed equation quite a bit.

Getting started with Android CLI

Android CLI is in preview. All the documentation and installation steps are at d.android.com/tools/agents.