Antigravity in Android Studio: What Rabbit 2 Changes and How to Set It Up

Google Antigravity became available as an integrated development agent inside Android Studio following the general availability release of version Rabbit 2 on October 28, 2026. The milestone establishes production support for the Bring Your Own Agent architecture, enabling direct connections between external coding models and the primary Android IDE.

Clarifying the execution boundary separates desktop IDE tooling from mobile operating system runtimes.

Clarifying the Mobile Misconception: IDE Integration Rather than an Operating System Agent

Social media discussions following the October 30, 2026 update frequently conflated Android Studio with the Android mobile operating system. The official Android Developers announcement establishes that Antigravity functions strictly inside the desktop development environment rather than as a background service running on mobile handsets or tablets. Third-party repositories on GitHub bearing names like Antigravity for Android remain unofficial community efforts without Google engineering endorsement.

Developers interact with the agent through standard desktop tool windows on Linux, macOS, and Windows workstations.

The software operates on the workstation hosting Android Studio, issuing structured commands to local project files, emulators, and build scripts. Understanding that boundary prevents mistaken expectations regarding on-device mobile agent automation.

The integration connects to existing development trees without requiring physical mobile test hardware to run agentic inference.

Chronological Evolution: From Android CLI at I/O to Stable Rabbit 2 BYOA

The arrival of Antigravity in Android Studio represents the culmination of a staged rollout across the 2026 engineering calendar. Google initiated foundational agent support during Google I/O in May 2026 by publishing the Android CLI 1.0 documentation alongside an official Android resource bundle for Antigravity. That initial bundle introduced command-line inspection routines and modular Android skills for terminal-based workflows.

Preview integration surfaced on September 24, 2026, when Google launched Bring Your Own Agent in the Canary release channel of Android Studio Rabbit 2.

The Canary phase allowed early teams to test external agent connections over the Agent Client Protocol before broad production readiness. Industry outlets such as xenospectrum and dev.to documented the transition from Canary testing to general availability across late October. On October 28, 2026, the Android Studio engineering team declared Rabbit 2 stable, graduating the multi-agent selection interface to production environments worldwide.

Three Distinct Workflows: Android Studio BYOA, Android CLI, and Google AI Studio

Software engineers evaluating Antigravity for Android development navigate three distinct tooling architectures. First, Android Studio Rabbit 2 provides deep IDE integration through Bring Your Own Agent. Within the editor, Antigravity directly invokes native development instruments including Gradle build execution, the Android Emulator, Logcat device log capture, and visual layout inspectors.

Terminal-centric developers instead operate through the standalone Android CLI 1.0 toolchain.

The CLI environment operates independently of any graphical IDE, enabling Antigravity CLI, Claude Code, or OpenAI Codex to navigate codebases, assemble projects, and run automated user Journeys from standard shell environments. That lightweight modality serves headless continuous integration pipelines and terminal-driven developers who bypass desktop IDE memory overhead.

The third development path exists within the cloud-hosted Google AI Studio guide ecosystem. In that web environment, the Antigravity Agent generates complete client-side Kotlin and Jetpack Compose mobile applications from natural language prompts. The system couples generated code with Firebase authentication, Cloud Firestore data storage, and App Check security before building signed APK packages for Google Play internal testing tracks.

Activation Guide: Configuring Antigravity Through the Agent Window and Tools Settings

Activating Google Antigravity inside Android Studio Rabbit 2 requires a five-step configuration sequence within the stable IDE build. Teams must first verify their installation is updated to the stable Rabbit 2 release distributed on October 28, 2026.

Engineers then display the dedicated agent interface by opening the primary Agent tool window located in the side dock.

Alternatively, developers navigate to the global configuration panel via Settings > Tools > AI > Agents on Linux and Windows, or Android Studio > Settings > Tools > AI > Agents on macOS. From the drop-down selector containing over 40 supported coding agents, choose Google Antigravity as the active provider.

The system then prompts for authentication credentials based on your organizational licensing model.

Once authenticated, the IDE establishes an active session over the Agent Client Protocol, allowing developers to dispatch prompts directly from the editor window.

Authentication Tiers, Token Pricing, and Corporate Claims Under the Agent Client Protocol

Authentication options for Google Antigravity in Android Studio span three distinct account pathways confirmed in primary Google documentation. Individual developers sign into the agent using a Google AI Pro or Google AI Ultra subscription account, which applies personal plan quotas directly to IDE tasks. Enterprise teams connect corporate Gemini Enterprise licenses, while API-centric organizations supply standard Gemini API keys to fund execution under usage-based, pay-per-token pricing models.

Competing coding agents configured inside the BYOA interface authenticate through their respective commercial providers.

Anthropic Claude Agent and OpenAI Codex require individual API keys or provider accounts governed by their own billing schedules, while Junie connects through its dedicated platform credentials. Meanwhile, the legacy built-in Android Studio Gemini agent continues to operate alongside external agents without requiring additional license purchases. Google does not publish a unified, flat-rate pricing plan covering all Bring Your Own Agent providers within the IDE interface.

Google claimed in its September 2026 engineering bulletin that selecting Google Antigravity delivers the optimal Gemini experience by granting access to the latest Gemini Flash 3.8 models and higher operational usage quotas. That statement represents Google corporate product positioning rather than an independently audited benchmark across real-world enterprise codebases. Engineering teams adopting Rabbit 2 should evaluate real token consumption and build diagnostic accuracy across their own local repositories before standardizing agent workflows.