Skip to content
AI.info

The Pulse

Android Studio Rabbit 2 Adds Support for More Than 40 Coding Agents

Google made Android Studio’s Bring Your Own Agent feature available in the stable Rabbit 2 release, with support for more than 40 coding agents. The update also adds an agent skills manager, LeakCanary assistance and AI-guided code review.

Android Studio Rabbit 2 Adds Support for More Than 40 Coding Agents

AI.info Team · Written with AI · fact-checked ·

“You can choose from over 40 coding agents — including Claude Agent, Codex from OpenAI, Junie, and Google Antigravity.”

Matthew Warner, Product Manager, Android Developer Experience

Google made its Bring Your Own Agent feature part of the stable Android Studio Rabbit 2 release on Oct. 28, letting developers select external coding agents from inside the IDE. The release moves the integration beyond the Canary preview Google introduced in September. It brings outside agents into the same workspace as Android Studio’s emulator, build systems and Logcat tools.

ACP opens Android Studio to more agents

The agents connect through the Agent Client Protocol, or ACP, an open protocol for linking agents with development environments. Google names Claude Agent, OpenAI’s Codex, Junie and Antigravity among the options, while its announcement says the list includes more than 40 agents. Developers can choose an agent in the Agent window or find one under Settings > Tools > AI > Agents.

Once connected, an agent can use Android Studio tools including the emulator, build systems and Logcat. Google says agents can also draw on Android skills—task-specific guidance for work such as migrating older XML-based interfaces to Jetpack Compose, upgrading Android Gradle Plugin versions and building adaptive layouts. The idea is to let developers choose an agent without giving up the IDE’s Android-specific tooling.

Rabbit 2 adds skills management and memory-leak help

The stable release adds a skills manager for discovering, installing and managing Android and Firebase skills from inside Android Studio. Google’s examples include migrating legacy views to Compose, upgrading to AGP 9, adapting layouts for tablets and foldables, and working with CameraX. Developers can open the manager from the Agent panel or the IDE’s settings.

Rabbit 2 also connects the built-in agent to LeakCanary, the memory-leak analysis tool. The integration produces explanations of possible leak causes and suggests code changes, keeping diagnosis and proposed fixes in the IDE. Google presents it as a way to move from a profiler finding to a potential repair without switching tools.

Google brings review into the agent workflow

Android Studio’s AI Change Review can start from agent changes, pending commits or the Git log. It first identifies recommended fixes, then offers a guided walkthrough that groups related changes across project files instead of presenting them only in alphabetical order. The feature addresses a problem Google itself identifies: faster code production can leave engineers with more changes to inspect and verify.

Google first described Bring Your Own Agent as a Canary preview on Sept. 24, listing Claude Agent, Codex and Antigravity as initial options and saying developers could connect other ACP-compliant agents through the registry. The company’s later announcement says Rabbit 2 is stable and ready for production use. Google has not supplied comparative performance results for the supported agents; the concrete change is that developers can now select from a larger set of agents within the stable IDE and give them access to Android Studio’s tools.

Agent choice sits beside Android’s built-in tools

The move does not replace Android Studio’s built-in Gemini experience. Google said in its earlier BYOA announcement that the built-in agent would remain available, while developers could connect alternatives and authenticate through the relevant provider. That leaves teams with a choice of agent and account arrangements rather than requiring a single model provider.

Rabbit 2’s significance is less a new coding model than a change in where developers can use outside agents: inside the stable Android IDE, alongside emulator testing, build tools, Android skills and code review. Google is putting the agent choice and the engineering work around it in the same product.

Sources

Explore

More articles