🤖 AI Tools
· 7 min read

Android CLI 1.0 Complete Guide: Build Android Apps with AI Agents (2026)

Google just shipped Android CLI 1.0 at Google I/O 2026, and it changes how AI agents interact with Android development. Instead of clunky workarounds or screen-scraping an IDE, any coding agent can now create projects, build APKs, deploy to devices, render Compose previews, and run UI tests — all from the terminal.

This isn’t another IDE. It’s a lightweight command-line interface designed specifically for agentic workflows. Whether you’re using Claude Code, Codex CLI, Antigravity, or a custom agent, Android CLI 1.0 gives them first-class access to Android Studio’s decade of tooling expertise — without ever opening a GUI.

What Android CLI 1.0 Does

Android CLI 1.0 is a bridge between AI coding agents and the Android development ecosystem. Here’s what it enables:

  • Project creation — Scaffold new Android projects with proper Gradle configuration, manifest files, and Compose boilerplate
  • Build and compile — Run full Gradle builds, generate APKs and AABs from the command line
  • Device deployment — Push builds to connected emulators or physical devices
  • Compose preview rendering — Generate visual previews of Jetpack Compose UI without opening Android Studio
  • UI test execution — Run Espresso and Compose UI tests headlessly
  • Semantic code analysis — Lint, inspect, and analyze Android-specific code patterns (resource references, manifest issues, API level compatibility)
  • Dependency management — Resolve, update, and audit Gradle dependencies

The key insight: all of this happens without opening Android Studio. The CLI exposes the same intelligence that powers the IDE — code inspections, build system integration, device management — through a terminal-native interface that agents can drive programmatically.

How Android CLI Works with AI Agents

The architecture is straightforward. Android CLI 1.0 acts as a tool layer that any agent can invoke through standard shell commands. There’s no proprietary protocol, no SDK to integrate, no authentication handshake with Google’s servers.

AI Agent (Claude Code / Codex / Antigravity)
    ↓ shell commands
Android CLI 1.0
    ↓ interfaces with
Android SDK + Gradle + ADB + Compose Compiler

When an agent runs android studio build, the CLI orchestrates the underlying Gradle daemon, SDK tools, and build cache — exactly as Android Studio would internally. The agent gets structured output (JSON or plain text) that it can parse and act on.

This design means Android CLI 1.0 is agent-agnostic. It doesn’t care which LLM is driving it. Any tool that can execute shell commands and read stdout can use it.

Supported AI Agents

Android CLI 1.0 works with every major coding agent available today:

Claude Code

Anthropic’s Claude Code can invoke Android CLI commands directly through its shell tool. Ask Claude Code to “build an Android app with a login screen” and it will scaffold the project, write Compose UI, build, and deploy — all using Android CLI under the hood.

Codex CLI

OpenAI’s Codex CLI integrates naturally since it already operates through terminal commands. The combination of Codex’s code generation with Android CLI’s build tooling creates a tight feedback loop: generate code → build → fix errors → deploy.

Antigravity

Google’s own Antigravity 2 has the deepest integration, as you’d expect. When paired with Gemini 3.5 Flash, Antigravity can leverage Android CLI with full context about Android best practices and API conventions. See our comparison of Antigravity vs Claude Code vs Codex for how they stack up.

Custom Agents

Building your own agent? Any script or program that can execute shell commands works. Python subprocess, Node child_process, or a Bash script — Android CLI doesn’t discriminate.

Key Commands and Features

The CLI centers around the android command with subcommands:

# Create a new project
android studio create --name "MyApp" --package com.example.myapp --compose

# Build the project
android studio build --variant debug

# Deploy to a connected device
android studio deploy --device emulator-5554

# Render Compose previews
android studio preview --composable LoginScreen

# Run UI tests
android studio test --type ui

# Analyze code for issues
android studio inspect --severity error

# List connected devices
android studio devices

# Check project health
android studio doctor

The android studio prefix is intentional — it signals that you’re tapping into Android Studio’s intelligence, not just wrapping raw Gradle commands. The CLI adds value on top: smarter error messages, structured output for agents, and Android-specific context that raw ./gradlew doesn’t provide.

Structured Output

Every command supports --output json for machine-readable results:

android studio build --variant debug --output json
{
  "status": "success",
  "artifact": "app/build/outputs/apk/debug/app-debug.apk",
  "duration_ms": 12340,
  "warnings": 2,
  "errors": 0
}

This makes it trivial for agents to parse results and decide next steps without regex-parsing human-readable logs.

Setup Guide

Getting Android CLI 1.0 running takes under five minutes:

Prerequisites

  • Android SDK installed (via Android Studio or sdkmanager)
  • Java 17+ (required for Gradle)
  • ADB in your PATH (for device deployment)

Installation

# Install via sdkmanager
sdkmanager --install "cmdline-tools;latest"

# Or via Homebrew (macOS)
brew install android-cli

# Verify installation
android studio --version
# Android CLI 1.0.0 (stable)

Agent Configuration

For Claude Code, add to your project’s tool configuration:

{
  "tools": {
    "android": {
      "command": "android studio",
      "description": "Android development CLI for building, testing, and deploying"
    }
  }
}

For Antigravity, Android CLI is detected automatically when present in PATH.

For Codex CLI, no configuration needed — it discovers available CLI tools at runtime.

Example: Building an App with an AI Agent + Android CLI

Here’s a real workflow using Claude Code + Android CLI 1.0 to build a weather app:

Step 1: Scaffold the project

You tell Claude Code: “Create an Android app that shows current weather for a given city using the OpenWeatherMap API.”

Claude Code runs:

android studio create --name "WeatherApp" --package com.example.weather --compose

Step 2: Generate the code

The agent writes Compose UI, a ViewModel, a Retrofit service, and wires up dependency injection — all as regular file writes.

Step 3: Build and check

android studio build --variant debug --output json

If there are errors, the agent reads the structured output, fixes the issues, and rebuilds. This loop typically converges in 1-3 iterations.

Step 4: Preview the UI

android studio preview --composable WeatherScreen --output png

The agent can inspect the rendered preview (or describe it to you) to verify the UI looks correct before deploying.

Step 5: Deploy and test

android studio deploy --device emulator-5554
android studio test --type ui --output json

End to end, this takes minutes. No manual coding, no IDE interaction. The agent handles everything through Android CLI 1.0.

Limitations

Android CLI 1.0 is impressive, but it’s not magic:

  • No visual layout editor — You can render previews, but there’s no drag-and-drop. Agents work in code, not pixels.
  • Emulator management is basic — You can deploy to running emulators, but creating/configuring AVDs still requires avdmanager separately.
  • Large projects may be slow — First builds still take time. The CLI doesn’t bypass Gradle’s compilation overhead.
  • Not a replacement for Android Studio — Complex debugging, profiling, and performance analysis still benefit from the full IDE. Google positions this as complementary.
  • Agent quality varies — The CLI is only as good as the agent driving it. A poorly prompted agent will still produce bad code, just faster.

FAQ

Is Android CLI 1.0 free?

Yes. Android CLI 1.0 is free and open source, distributed as part of the Android SDK command-line tools. No license fees, no usage limits.

Does Android CLI replace Android Studio?

No. Google explicitly positions Android CLI as complementary to Android Studio. The CLI is designed for agentic and automated workflows. Android Studio remains the primary tool for interactive development, debugging, and profiling.

Which AI agents work with Android CLI?

Any agent that can execute shell commands works with Android CLI 1.0. This includes Claude Code, Codex CLI, Antigravity, and any custom agent you build. There’s no vendor lock-in.

Can I use Android CLI without an AI agent?

Yes. While designed for agentic workflows, Android CLI works perfectly as a standalone developer tool. You can run all commands manually from your terminal for scripting, CI/CD pipelines, or personal preference.

Does Android CLI support Kotlin Multiplatform?

Android CLI 1.0 focuses on native Android development with Jetpack Compose. Kotlin Multiplatform support is not included in the initial stable release but is on Google’s roadmap based on I/O 2026 discussions.

How does Android CLI compare to just using Gradle from the command line?

Android CLI wraps Gradle but adds significant value: structured JSON output for agents, Compose preview rendering, semantic code analysis, smarter error reporting, and device management. Raw Gradle gives you builds; Android CLI gives you the full Android Studio intelligence without the GUI.

What This Means for Android Development

Android CLI 1.0 is part of Google’s broader push toward agent-first development tooling announced at Google I/O 2026. Combined with Gemini 3.5 Flash and Antigravity, Google is building an ecosystem where AI agents are first-class participants in the development process.

For Android developers, this means you can now deploy AI agents to production workflows that handle everything from prototyping to testing. The barrier between “idea” and “running app” just got significantly thinner.

Check our best AI coding tools for 2026 roundup for how Android CLI fits into the broader landscape of agent-powered development.

Android CLI 1.0 was released on May 19, 2026 at Google I/O. This guide will be updated as new features ship.

You might also like

Google Antigravity 2.0 Complete Guide: The Agent-First Coding Platform

Everything about Google Antigravity 2.0 — the new desktop app, CLI tool, SDK, and how it replaces Gemini CLI. Setup, pricing, features, and comparison with Claude Code and Codex CLI.

Antigravity SDK Guide: Build Custom AI Agents with Google's Managed Agent API (2026)

How to build custom AI agents with the Antigravity SDK. Managed agents on the Gemini API that reason, execute code, manage files, and browse the web in secure sandboxes.

Gemini 3.5 Flash Complete Guide: Google's Fastest Frontier Model

Everything developers need to know about Gemini 3.5 Flash — benchmarks, pricing, API setup, thinking mode, and how it compares to GPT-5.5 and Claude Opus 4.7. Released at Google I/O 2026.

Gemini Spark: Google's 24/7 Personal AI Agent Explained

What is Gemini Spark? Google's new personal AI agent that connects to Gmail, Calendar, and apps to take action on your behalf. How it works, pricing, and availability.