Android Studio Quail 2: Parallel Agents & LeakCanary Guide

Android Studio Quail 2 reached stable status in July 2026. The release redesigns Agent Mode so you can run multiple AI conversations at once. It also embeds LeakCanary in the Profiler and links App Quality Insights directly to the agent for crash fixes.

Developers no longer wait for one agent task to finish before starting the next. Memory leak analysis moves off the device and onto your computer, cutting trace time by up to five times.

Set Up Android Studio Quail 2

Download the latest stable build from the official Android Studio page. Install it over your current version or side-by-side if you prefer. Open an existing project or create a new one with the standard template.

Sign in with a Google account that has Gemini access. Agent Mode appears in the tool window on the right. Confirm the selected model in the chat settings. Quail 2 lets each conversation use a different model.

Run Parallel Agent Chats

Open Agent Mode. Click the + icon or choose File > New > New Agent Tab to start a second conversation. Each tab runs independently.

Start a long refactor in the first tab. Switch to the second tab and ask the agent to update ProGuard rules. Open a third tab and request documentation for a module. All three continue without blocking each other.

Use the History icon to switch between active tasks. Watch for file conflicts if two chats edit the same source files. Worktree support is not available yet, so review changes carefully before applying them.

Test model choice per chat. Point one conversation at a faster model for quick edits and another at a stronger model for architecture decisions. Check Android Bench for performance data on common Android tasks.

Profile Memory Leaks with LeakCanary

Start a profiling session on a device or emulator. Open the Profiler tool window and select the new LeakCanary task. The analysis runs on your development machine instead of the phone.

Reproduce the leak in the app. The Profiler shows an interactive, color-coded trace. Grouped occurrences and estimated memory loss appear next to each retained object.

Click Go to declaration on any leaking reference to jump straight to the source line. Select Fix with Agent. The Gemini agent reads the trace, explains the retained reference, and proposes the code change that clears it.

Review the suggested edit before applying it. Common fixes include removing listeners in onDestroy or clearing static references after the Activity ends.

Fix Crashes with App Quality Insights

Open the App Quality Insights panel. Select a crash report. The panel shows a short summary of the failure.

Click See more to open a dedicated agent chat. The agent pulls the full stack trace and your local source. It explains the failure path step by step.

Click Fix with AI. The agent drafts a plan, waits for your approval, applies the code changes, and can verify the result on an emulator. This closes the loop from crash report to patched build inside the IDE.

Tips for Daily Use

Keep parallel chats focused. Use one for exploration and another for production edits. Apply changes from one chat before starting a conflicting edit in another.

Run LeakCanary profiling on representative user flows rather than every build. The five-times speed gain shows up most when you profile repeatedly during a session.

Combine AQI fixes with parallel chats. Let one agent research the crash while another updates tests that cover the same path.

Review known issues on the Android Studio site before upgrading large projects. Quail 2 inherits IntelliJ platform improvements, but project-specific Gradle settings may still need adjustment.

For related performance work, see the guide on Android baseline profiles.

Conclusion

Android Studio Quail 2 turns Agent Mode into a multi-threaded assistant. Parallel chats remove the wait between tasks. Native LeakCanary moves heavy analysis off the device. App Quality Insights hands the agent the exact crash context it needs to propose and apply fixes.

Download the stable build, open a project, and start a second agent tab. The time saved on leaks and crashes compounds across every release cycle.

Sources

• Android Developers Blog: Android Studio Quail 2 is Stable
• Android Studio release notes for Quail 2
• LeakCanary documentation