Android Studio Rabbit 2 canary adds Bring Your Own Agent through Agent Client Protocol. Codex, Claude Agent, Google Antigravity or another ACP-compatible agent can receive project graphs, build setup, diagnostics, Compose Preview, Android SDK tools and emulator control from the IDE. Agents can edit files, run tests, browse, delegate and persist sessions or skills under granular approval prompts. The feature was published two minutes before the prior checkpoint and was recovered through the overlap window.
Android Studio opens its IDE context to ACP-compatible agents
Android Studio Rabbit 2 canary adds Bring Your Own Agent through Agent Client Protocol. Codex, Claude Agent, Google Antigravity or another ACP-compatible agent can receive project graphs, build setup, diagnostics, Compose Preview, Android SDK tools and emulator control from the IDE. Agents can edit files, run tests, browse, delegate and persist sessions or skills under granular approval prompts. The feature was published two minutes before the prior checkpoint and was recovered through the overlap window.
Availability: Android Studio Rabbit 2 canary preview
Imported from the existing research archive. Migration preserves the recorded judgment and is not a fresh verification.
What this means for you
For Android teams, the IDE can become the stable source of project-specific context while the reasoning agent remains replaceable. Trial it in a disposable branch: canary maturity and broad tool access make approval boundaries more important than model choice.
Evidence & related material
Technical details & scores
| Availability | Android Studio Rabbit 2 canary preview |
|---|---|
| Protocol | Agent Client Protocol (ACP) |
| Agents | Codex, Claude Agent, Google Antigravity and other ACP-compatible agents |
| Ide Context | project graph, builds, diagnostics, Compose Preview, Android SDK and emulator |
| Controls | granular approval prompts |
| Boundary | recovered from retrieval overlap |