Android Studio Rabbit 2 Opens the Door to More AI Coding Agents

What shipped in the stable release?

Google identifies Rabbit 2 (2026.2.2) as the current stable version of Android Studio. The release adds Bring Your Own Agent, an Android skills manager, AI-assisted Change Review, deeper LeakCanary integration and stable Android XR emulators for several device types. The company also announced improvements to Android CLI, but those command-line features and the Studio release should not be assumed to have identical workflows.

Stable-channel status means these features are available in the stated IDE release; it does not prove that every third-party agent, authentication method or organizational policy will work identically on every machine. Check agent compatibility and project requirements before a team-wide rollout.

Sources: Your favorite agents are now integrated in Android Studio · Agentic and Flexible: A next era of Android development · Android Studio Rabbit 2 release notes

Bring Your Own Agent changes the center of the workflow

Rabbit 2 can connect agents that support the Agent Client Protocol (ACP). Google names Claude Agent, OpenAI Codex, Google Antigravity and Junie among the options and describes a registry of more than 40 coding agents. Developers can choose their agent rather than being limited to a single model from the IDE vendor.

The meaningful integration is with the environment: agents may use Android Studio's build diagnostics, SDK tools, terminal, emulator and project context to complete tasks. That can be more effective than pasting a compiler error into a separate chatbot. It also increases the importance of reviewing exactly what access an agent receives.

The integration is a product capability claim from Google, not an independent performance comparison. We have not run a hands-on benchmark of the supported agents or measured token savings.

Sources: Your favorite agents are now integrated in Android Studio · Agentic and Flexible: A next era of Android development

How developers can start without overcommitting

Google's setup path is to update Android Studio to Rabbit 2, open the agent window, choose an available agent or use Settings > Tools > AI > Agents, then authenticate. Access may require an agent-specific subscription, API key or enterprise arrangement. A supported agent does not mean that the agent's commercial service is free.

Start with a disposable branch and a narrow task: explain a build failure, propose a small Compose change or identify a clear resource leak. Inspect the proposed diff and test it before accepting it. When an agent can run shell commands or manage an emulator, treat the connection as a real tool permission, not just an ordinary chat feature.

Sources: Your favorite agents are now integrated in Android Studio · Android Studio Rabbit 2 release notes

Skills and code review are part of the story

The updated skills manager can discover, install and manage task-specific guidance within Android Studio. Google lists workflows including XML-to-Compose migration, adaptive layouts and integration work. Skills can make a task repeatable, but guidance files should be reviewed like any other tool-supplied instructions before they are allowed to influence code edits.

AI Change Review is intended to help navigate and evaluate changes from agents, pending commits or Git history. Google says it can identify suggested fixes and build a guided walkthrough of related code changes. That is useful for reducing review friction, but the developer remains responsible for testing, security review and merge decisions.

LeakCanary integration helps the built-in agent explain suspected memory leaks and suggest corrections from profiling data. An explanation or proposed fix is still a hypothesis until validated with the profiler and a representative test.

Sources: Your favorite agents are now integrated in Android Studio · Android Studio Rabbit 2 release notes

Android XR tooling gains a more practical testing loop

Rabbit 2 also brings stable emulators for XR, audio and display glasses. The tooling can simulate device inputs and environments, with options for customized visual scenes and privacy indicators in supported emulators. That gives developers a way to iterate on interfaces before obtaining every physical device.

An emulator is valuable for layout and workflow checks, but it cannot reproduce all physical constraints of wearable hardware, such as real-world optics, battery behavior, sensors and network conditions. Hardware testing remains important before a product is considered ready.

Sources: Your favorite agents are now integrated in Android Studio · Android Studio Rabbit 2 release notes

Android CLI expands what agents can verify

Google's Android Dev Summit overview describes Android CLI additions such as remote device streaming, Jetpack Compose previews and system tracing. In principle these features let a coding agent move beyond generating source code toward checking how changes render and perform.

The practical lesson for teams is to establish a trusted test loop: compile, run relevant tests, inspect logs, examine the actual interface and require a human decision for risky changes. Tool availability does not remove the need to choose appropriate tests or to account for flaky environments.

Sources: Agentic and Flexible: A next era of Android development

The four questions to ask before enabling agent access

First: what can the agent read and change? Inspect file permissions, terminal access, account connections and any attached tools. Second: how are approvals enforced? A prompt requesting caution is not a substitute for a permission boundary. Third: where do prompts, files and logs go? Use the correct vendor and plan documentation rather than assuming every supported agent shares Google's data handling. Fourth: can the team reproduce the result with build output, tests and a reviewable diff?

A useful pilot measures concrete outcomes such as time to resolve a known failing test, number of incorrect edits and effort required to review changes. Do not claim productivity gains or code quality improvements without a repeatable comparison.

Sources: Your favorite agents are now integrated in Android Studio · Android Studio Rabbit 2 release notes

A more flexible IDE is still a responsibility

The emerging pattern is a development environment that exposes its tools to multiple agents, while leaving developers free to choose which system does the work. That flexibility can reduce switching costs and encourage better workflows, but it also places more responsibility on permissions, review and reproducibility.

For most teams, the best first use is a small, verifiable coding task—not unattended changes to production infrastructure. Rabbit 2 is a notable release because of how it connects agents to the Android toolchain; whether it improves a particular team's output remains a question for that team's own tests.

Sources: Your favorite agents are now integrated in Android Studio · Agentic and Flexible: A next era of Android development · Android Studio Rabbit 2 release notes