Google announced on October 28, 2026 that Android app teams can now connect compatible third-party AI coding agents to the stable version of Android Studio, its app-development environment. The Rabbit 2 release brings the choice of agent into the same place developers build and debug their apps.
The feature, called Bring Your Own Agent, first appeared in Canary preview on September 24. Rabbit 2 moves that workflow into the stable channel.
What connected agents can do
Google lists more than 40 compatible agents, including Claude Agent, OpenAI Codex, Junie and Google Antigravity. These agents can carry out coding tasks through tools, rather than only return text suggestions.
According to Google’s release notes, connected agents can use project-structure information, build diagnostics and emulator controls. The launch announcement also names Logcat, the app and device log viewer. An emulator simulates an Android device, so this is access to the build-and-debug environment as well as the code.
The connection uses Agent Client Protocol (ACP), a standard for communication between coding agents and editors.
Your agent account, a separate session
Google says its built-in agent remains available without an additional charge. For other agents, its account guidance allows consumer and enterprise plans subject to the provider. That does not mean third-party subscriptions or unlimited usage are included.
For a team already paying for a coding agent, the practical first check is whether that provider supports its account in Studio and what usage limits apply. Compatibility alone is not evidence of lower costs or identical features across agents.
There is also an important distinction between reusing an account and continuing a conversation. Google’s quickstart says Studio launches a separate agent instance; it does not attach to one already running in a terminal. Teams should therefore not assume a terminal conversation will automatically continue inside Studio.
Getting started—and a documentation conflict
Google’s launch instructions direct users to select an agent in the agent window or Settings > Tools > AI > Agents, then authenticate.
The release page still tells users to install the latest Canary build in its setup subsection, even though the same page and the October 28 announcement identify Rabbit 2 as stable. That inconsistency remains unresolved; the dated launch announcement explicitly points users to the stable release.
For a different approach to reviewing agent-generated changes, see Replit’s video-backed code proposals for workplace teams.