---
type: "post"
id: "google-antigravity-agent-now-available-in-stable-android-74cd09"
slug: "google-antigravity-agent-now-available-in-stable-android-74cd09"
title: "Google Antigravity agent now available in stable Android Studio Rabbit 2 via Bring Your Own Agent"
description: "Google has made Android Studio Rabbit 2 stable with Bring Your Own Agent, a selection layer for more than 40 ACP-compliant coding agents."
retrieval_nugget: "Google has made Android Studio Rabbit 2 stable with Bring Your Own Agent, a selection layer for more than 40 ACP-compliant coding agents. Antigravity, Claude Agent, OpenAI Codex, and Junie can work with Android Studio’s emulator, build systems, Logcat, and Android-specific skills, making the IDE a shared operational surface rather than a single-vendor assistant."
published_at: "2026-10-30"
updated_at: "2026-10-30"
record_date: "2026-10-30"
date_kind: "published_at"
topics: ["google","coding-agents","claude"]
entities: ["Google","Android Studio Rabbit 2","Bring Your Own Agent","Google Antigravity","Claude Agent","OpenAI Codex","Junie","Agent Client Protocol"]
related_patterns: ["harness-architecture-outlives-model-choice","skills-become-portable-capability-layer"]
novelty_label: "new_fact"
what_changed: "Google Antigravity is now available as a Bring Your Own Agent option in stable Android Studio Rabbit 2, alongside other agents."
prior_refs: ["memory:16251695-4b26-8572-ab36-02f83f08ec94","memory:9b16cc91-919e-81c9-a963-f4404b891817","memory:fa7bae1d-7823-8795-a3db-1094be8d1a5b"]
source_url: "https://developer.android.com/blog/posts/ai-agents-android-studio-integration"
source_urls: ["https://developer.android.com/blog/posts/ai-agents-android-studio-integration"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:google-antigravity-agent-now-available-in-stable-android-74cd09"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/google-antigravity-agent-now-available-in-stable-android-74cd09/","markdown":"https://newruntime.com/posts/google-antigravity-agent-now-available-in-stable-android-74cd09.md","json":"https://newruntime.com/posts/google-antigravity-agent-now-available-in-stable-android-74cd09.json"}
---

# Google Antigravity agent now available in stable Android Studio Rabbit 2 via Bring Your Own Agent

## Retrieval answer

Google has made Android Studio Rabbit 2 stable with Bring Your Own Agent, a selection layer for more than 40 ACP-compliant coding agents. Antigravity, Claude Agent, OpenAI Codex, and Junie can work with Android Studio’s emulator, build systems, Logcat, and Android-specific skills, making the IDE a shared operational surface rather than a single-vendor assistant.

## Summary

Google has made Android Studio Rabbit 2 stable with Bring Your Own Agent, a selection layer for more than 40 ACP-compliant coding agents. Antigravity, Claude Agent, OpenAI Codex, and Junie can work with Android Studio’s emulator, build systems, Logcat, and Android-specific skills, making the IDE a shared operational surface rather than a single-vendor assistant.

## What happened

Android Studio Rabbit 2 is now stable and available for production use. Google’s release includes Bring Your Own Agent (BYOA), alongside stable Android XR emulator work, a LeakCanary update, a skills manager, AI code review, and other features. The relevant change for teams using coding agents is that Android Studio now presents itself as a host for ACP-compliant agents rather than only as a place for its own built-in assistant experience.

Google says developers can choose from more than 40 coding agents through BYOA. The named examples are Claude Agent, Codex from OpenAI, Junie, and Google Antigravity. A developer can open the agent window and select an agent, or navigate to Settings > Tools > AI > Agents, then authenticate and send a prompt. Google frames the choice around workflow flexibility: a team may prefer a particular agent, seek a lower-cost option for a project, or need a provider that fits an enterprise agreement.

The integration is consequential because the agents are not described as isolated chat panes. They have access to Android Studio tools including the Android Emulator, build systems, and Logcat. They can also use Android skills to complete more complex tasks. That places agent selection alongside the environment where Android developers build, run, inspect, and debug applications.

Rabbit 2 also adds a skill-management surface inside Android Studio. Developers can discover, install, and manage Android and Firebase agent skills, with granular control over specialized workflows and procedural guidance available to an agent. Google lists skills for migrating legacy XML Views to Jetpack Compose, upgrading to Android Gradle Plugin 9, implementing adaptive layouts for foldables and tablets, and integrating CameraX and Firebase services. The skills manager is reachable from the Agent panel, by using @ in chat, or through Settings > Tools > AI > Skills Manager.

Finally, Google describes a direct LeakCanary integration with the built-in agent. In the Profiler’s LeakCanary task, the integration can provide narrative explanations of memory-leak causes and suggest code changes. The release therefore combines agent choice, IDE tool access, and packaged Android-specific procedures in a stable Android Studio version.

## What the archive adds

This is a new access point in a known Antigravity story, rather than a restatement. [Google Antigravity custom agents](https://newruntime.com/posts/google-antigravity-custom-agents/) covered Antigravity 2.0’s first-class custom agents in its IDE and CLI. Rabbit 2 extends the practical distribution surface: Antigravity is now one selectable agent among ACP-compatible options inside Android Studio. A separate earlier note on [Antigravity in Gemini for macOS](https://newruntime.com/posts/gemini-4-argon-also-brings-major-improvements-in-2795ad/) likewise tracked the coding interface moving beyond one dedicated environment.

## Trend signal

This supports [Harness architecture outlives model choice](https://newruntime.com/patterns/harness-architecture-outlives-model-choice/). Android Studio is retaining the durable work surface—emulation, builds, logs, and Android procedures—while allowing the coding agent to vary. It also supports [Skills become a portable capability layer](https://newruntime.com/patterns/skills-become-portable-capability-layer/): the release makes skills a managed, discoverable package of task guidance rather than leaving every Android workflow to an unstructured prompt.

## Why now

Google announced Rabbit 2 as stable while directing readers to Android Dev Summit material being livestreamed that day. The timing gives Google a production-ready Android Studio release on which to demonstrate agent workflows, XR development, skills, and enterprise-oriented development tooling together.

## Connections to other events

The previous Antigravity custom-agents release emphasized specialized agents that can act, verify, and run in parallel. BYOA does not establish that every selected agent has those same properties, but it gives Android developers a common IDE location in which to select Antigravity alongside other ACP-compliant coding agents. The prior Gemini-for-macOS note showed Antigravity’s coding interface crossing into a general assistant; Rabbit 2 shows a complementary direction, with Antigravity entering another developer environment.

## Why it matters

For an Android team, the immediate value is not that every agent will perform equally well. It is that experimentation can happen without abandoning the development environment that already holds the emulator, build feedback, device logs, and project workflow. Teams can evaluate agents against the same Android task and the same operational tools, while retaining a route to use a provider required by procurement or preferred for cost.

The skills manager is equally important. Android work often contains repeatable migrations, framework upgrades, layout changes, and service integrations where a free-form prompt is a poor substitute for a maintained procedure. Packaging those procedures as selectable skills can make an agent’s behavior more consistent and make the team’s Android conventions easier to reuse. The release shifts some differentiation from the model alone toward the combination of agent, IDE tools, and task-specific guidance.

## What happens next

- **More Android teams will compare multiple ACP agents on the same build-and-debug tasks.** (3 months, 70%). Watch for: additional named agents or Android Studio guidance on evaluation and supported workflows.
- **Skill libraries will become a more visible way to standardize Android migrations and integrations.** (6 months, 65%). Watch for: new Android or Firebase skills and expanded management controls.

## Limits and uncertainty

Google says BYOA supports more than 40 coding agents, but the supplied release does not provide a complete agent list, feature parity table, pricing, performance comparison, or security model for each provider. It does not establish that every agent can use every IDE capability in the same way, nor does it specify which Android skills work with which selected agents. The announcement names access to the Emulator, build systems, Logcat, and Android skills, but it does not quantify task success, time saved, or quality of suggested code changes. Teams should therefore treat the integration as a new evaluation surface, not proof that a particular agent is suitable for production changes.

## Skill to build now

Create one bounded Android evaluation task that includes a build failure, a Logcat symptom, and a required repository change. Run it through two available BYOA agents in the same Android Studio project, using the relevant installed Android skill where applicable. Record whether each agent reaches a compiling change, whether it correctly interprets the logs, and how much review or correction the result requires. This turns agent choice from a provider preference into a repeatable engineering comparison.

## Reader takeaway

Android Studio Rabbit 2 makes the IDE an agent-neutral working surface: developers can choose among ACP-compatible coding agents while keeping access to Android-specific tools and managed skills. The useful next move is to test agents on a real, bounded Android workflow—not to assume that access alone produces interchangeable results.

## Open question

How consistently will third-party ACP agents receive and use Android Studio tools and Android skills, and which controls will teams need before granting them access to production repositories?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Google](https://newruntime.com/topics/google.md): Explore the google topic hub.
- topic hub: [Coding Agents](https://newruntime.com/topics/coding-agents.md): Explore the coding-agents topic hub.
- topic hub: [Claude](https://newruntime.com/topics/claude.md): Explore the claude topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)