Android Studio Rabbit 2 Goes Stable with Bring Your Own Agent and XR Emulators

Android Studio Rabbit 2, version 2026.2.2, moved to the stable channel on October 28, 2026. The release is the first stable build to treat third party coding agents as a first class part of the IDE rather than a plugin workaround, and it is also the first to ship glasses emulators as stable tooling.

For Flutter developers the relevant question is narrower than the headline list. The Android toolchain sits underneath every Flutter Android build, and the IDE is where most of the debugging happens even when the Dart side is driven from a terminal. Changes to the emulator, the profiler, and the agent integration reach Flutter workflows through that shared surface.

Bring Your Own Agent Over ACP

The headline feature is Bring Your Own Agent. Rabbit 2 lets you connect an external coding agent to the IDE through the open Agent Client Protocol. The supported defaults at launch are Claude Agent, OpenAI Codex, and Google Antigravity, and the protocol is open, so any ACP compliant agent can be registered from Settings, under Tools, then AI, then Agents.

The integration is deeper than a terminal panel. The chosen agent receives the full project graph, build diagnostics, and emulator controls from the IDE. That means an agent can read the actual Gradle failure instead of inferring it from pasted text, and it can drive a virtual device as part of a fix. Google's stated benefit is faster execution and lower token consumption, which follows directly from the agent receiving structured diagnostics rather than re-discovering them.

Authentication is deliberately permissive. You can sign in with a personal API key or a consumer subscription, or use an enterprise subscription, while the built in agent stays available at no extra charge. For teams already paying for one agent vendor, that removes the awkward choice between the IDE assistant and the agent they actually standardised on.

• Default agents available from the agent window: Claude Agent, Codex, and Antigravity
• Additional ACP compliant agents can be added from the agent registry in settings
• IDE context passed to the agent covers project structure, build diagnostics, terminal execution, and emulator management

LeakCanary Talks to the Agent

The second feature is smaller and arguably more useful day to day. Rabbit 2 integrates LeakCanary directly with the AI agent inside the Profiler. Instead of presenting a raw leak trace, the integration produces a narrative explanation of what is retaining the object and suggests specific code changes to correct it.

Memory leaks in Flutter apps on Android usually surface through the platform layer rather than the Dart layer, so this is a shared concern. A retained view hierarchy never appears in Dart DevTools, and the retention chain is often four or five frames long with framework internals in the middle.

Rabbit 2 also makes Android skills manageable inside the IDE. You can discover, install, and manage skills that give the agent specialised procedural guidance, with granular control over which ones are active. That mirrors the direction Flutter took when it shipped skills for Dart and Flutter, and it pushes the same idea into the Android side of the workflow.

Glasses Emulators Reach Stable

The largest section of the release notes covers XR. Emulators for XR glasses, audio glasses, and display glasses are now stable, and all three launch by default as embedded emulators inside the Running Devices tool window rather than as separate windows.

For XR glasses, the emulator simulates electrochromatic dimming through an Environment Visibility slider with five opacity levels from fully transparent to maximum dimming, alongside a passthrough mode. Input can be switched between hand tracking, which simulates pinch and raycast pointer events, eye tracking, which simulates gaze focus and selection, and hardware input from a connected mouse and keyboard. Each mode has its own cursor so the difference is visible while testing.

Display glasses get a custom environment feature. You can load standard equirectangular 360 degree photos as JPEG or PNG, use a flat 2D still, or stream a live camera feed, then rotate the view inside the scene to see how interface elements render under different real world lighting. Audio and display glasses emulators also show hardware LED indicators for microphone and camera access directly on the emulator frame.

• Device Manager now shows paired phone and glasses devices in a nested hierarchy and persists pairing across restarts
• The Pairing Assistant no longer requires signing in to a Google Account
• A Basic Display Glasses Activity template pre-configures Jetpack Compose Glimmer and Jetpack Projected dependencies
• Unpaired glasses devices automatically prompt to launch the Pairing Assistant

Smaller Changes Worth Knowing

One quality of life change is easy to miss and immediately noticeable in use. Double-clicking empty space in the Running Devices tool window now resizes it to fit the device tightly, with docked windows adjusting width or height depending on the dock edge and split views rebalancing their internal splitters.

The compatibility surface also moved. Rabbit 2 supports AGP 7.1 through 9.5, one step further than Rabbit 1 at 9.4, so a recent Android Gradle Plugin is a normal requirement for Flutter Android builds.

Cloud service integrations carry their own clock. Gemini in Android Studio, Play Vitals, and Firebase Crashlytics are available only on the latest stable channel plus major versions released in the previous ten months. Support for Panda 1 has already been deprecated and will be disabled entirely at the next major release.

The practical upgrade path is Help, then Check for Updates. Rabbit 1 users moving forward should verify their AGP version first, then their Gradle and Kotlin versions, because the IDE will refuse to build a project whose AGP falls outside the supported window. After that, the agent registry is a two minute setup and the profiler integration is already on.