Android Studio Rabbit 2: Run 40+ AI Agents in Your IDE

Android Studio Rabbit 2 went stable on October 28, and the headline feature is not a new refactor tool or a smarter lint pass. It is Bring Your Own Agent: install Claude Agent, Codex, Antigravity, or any of 40+ coding agents directly in the IDE and switch between them without touching your project. The lock-in is gone. The mechanism behind it — Agent Client Protocol (ACP) — just hit 42 agents across 19 IDEs. For Android developers who have already built workflows around tools like Claude Code, this changes the calculus entirely.

What BYOA Actually Does

Google’s built-in assistant still ships with Android Studio. BYOA does not replace it — it opens a parallel track. Through ACP, Android Studio acts as the host, launching your chosen agent as a subprocess and communicating over stdin/stdout using JSON-RPC 2.0. When a session starts, the IDE hands the agent the full project graph, build configuration, and platform details. The agent uses that context to filter to relevant files, which matters: smaller context means lower latency and fewer wasted tokens on irrelevant code.

Setup is three steps: update to Rabbit 2 (version 2026.2.2), open Settings > Tools > AI > Agents, and install from the marketplace. Personal API keys and enterprise subscriptions both work. You are not being pushed into a new billing relationship.

What Agents Can Do Inside Android Studio

This is where Android Studio’s BYOA implementation pulls ahead of generic ACP support. Agents are not just reading files and suggesting edits. They have native access to the full Android development stack:

• Emulator control — manage virtual devices without leaving the IDE
• Logcat — live log streaming and analysis in-context
• Compose Previews — render UI without a physical device
• Build diagnostics — build-system-aware error diagnosis, not just copied stack traces
• LeakCanary integration — the agent sees memory leak diagnostics and suggests fixes
• Android Skills Manager — 30+ preloaded skills across 20+ areas, including the official Android Knowledge Base

Google reports 77% faster UI task completion using the android preview tool. Take that figure as directional. Test it on your own workload before quoting it in a planning doc.

ACP Is Not MCP — This Confusion Is Everywhere

Two protocol names that look similar and do completely different things:

• ACP (Agent Client Protocol) — connects editors to coding agents. This is what Android Studio implements.
• MCP (Model Context Protocol) — connects agents to external tools and data sources. Anthropic’s protocol, not competing with ACP.
• A2A (Agent2Agent) — enables agent-to-agent delegation.

These protocols stack. In a typical agentic Android dev setup, ACP handles the IDE ↔ agent channel, MCP handles the agent ↔ tools channel, and A2A handles multi-agent delegation. They are not competing standards — they address different layers of the same problem.

The CLI Route for CI/CD

If you work outside the IDE — in a CI pipeline, a remote machine, or a terminal-first workflow — the Android CLI plugin is the path. It is now an official ACP plugin for Claude Code, Codex, and Antigravity.

For Claude Code:

claude plugin marketplace add android/android-cli-plugin
claude plugin install android-cli@android-cli-plugin
android init

For Codex:

codex plugin marketplace add android/android-cli-plugin
codex plugin add android-cli@android-cli-plugin
android init

The CLI route supports remote physical device access via Firebase, Compose Preview rendering in terminal, and LeakCanary-powered profiling. It is the right path for teams running automated mobile testing in CI.

The Gotchas Nobody Is Covering

The official coverage of Rabbit 2 is enthusiastic. Here is what the press releases leave out.

Stability is not settled. Independent community reports lean negative on early stability — the kind of rough edges typical of a new stable release, not a production-hardened one. The Android CLI user count grew 10x, but most of that came from a single viral post, not from sustained production use.

Your data terms are not Google’s terms. When you connect Claude Agent, your data moves under Anthropic’s terms of service. Same for Codex under OpenAI’s. Verify this with your own legal team before connecting a production project — Google’s Gemini Enterprise guarantees do not extend to third-party agents.

Gate physical device access. The android device remote capability provisions real hardware via Firebase. Treat it like git push — configure it to require manual approval rather than running autonomously.

Plugin security matters. Install the Android CLI plugin only from Google’s official namespace: android/android-cli-plugin. Do not copy plugin names from search results or unofficial documentation.

What This Means for the IDE Ecosystem

ACP at 42 agents and 19 clients is past the point where it can be dismissed. VS Code is the notable holdout — Microsoft has opted for vendor-specific integrations rather than the open protocol. That is a defensible business decision and also a constraint: VS Code users do not get the same agent portability that Android Studio and JetBrains users now have.

IDE vendors have historically used built-in AI assistants as retention tools — the better the assistant, the stickier the editor. ACP decouples that. Android Studio’s bet is that the platform-native integrations — Emulator, Logcat, Compose Preview, LeakCanary — are the real moat. The agents are commodities. The IDE-layer tools are not.