Android Studio Rabbit 2 brings coding agents into the IDE, in Canary

Google added Bring Your Own Agent (BYOA) to Android Studio Rabbit 2 Canary 2, announced on September 24, 2026. Android developers can connect coding agents including Codex, Claude Agent and Google's Antigravity inside the IDE. The practical change is that a chosen agent can receive Android Studio's project and build context and use its development tools. It is a Canary preview, so teams should test that integration on a representative project before treating it as a replacement for their established setup. Google's announcement and Rabbit 2 release notes describe the feature; neither is an independent productivity test.

From choosing a model to connecting an agent

Android Studio already supported custom AI models. BYOA changes the unit of integration: a developer can connect an agent that handles a sequence of coding tasks, rather than only selecting a model for the IDE's existing assistant. Google names Codex, Claude Agent and Antigravity as built-in choices, and says other agents can connect if they support the open Agent Client Protocol (ACP). The Studio agent remains available. The agent provider's account or API access still determines how that agent is authenticated and billed; the release does not make every provider's service interchangeable.

This distinction matters when a task crosses files, Gradle configuration and a running device. Google says Studio can pass the project graph and build details through ACP and expose build diagnostics, SDK tools, Compose previews and emulator control. An agent can then work with information the IDE already has, instead of relying solely on a pasted error or a generic repository search. Google's claim that this can save tokens or speed work is plausible, but the announcement supplies no cross-agent benchmark for a reader's own project.

The useful test is a complete Android task

For a trial, pick a small change with a checkable result: fix a build error, adjust a Compose screen, or reproduce a bug in the emulator. Observe what project information the agent receives, which tools it invokes, the edits it makes and whether the build or preview actually passes. Review the resulting diff and test the app yourself. That comparison reveals more than a short prompt demo because the promised advantage lies in the handoff between agent, build system and device.

Google's preview guidance says Canary builds are early releases and can be installed alongside stable Studio. The release notes identify BYOA in Rabbit 2 Canary 2; they do not place it in the stable Quail 4 release. If your team needs the current stable IDE, our Quail 4 coverage explains its bundled Android skills and local Gemma 4 option. BYOA is a separate preview choice, and the value of switching agents depends on the tools and permissions your provider supports in practice.