Android Studio Quail 4 Canary 4 Arrives with AI Agent and Profiler Fixes

Google has released Android Studio Quail 4 Canary 4 to the Canary channel, continuing the rapid iteration of the next-generation IDE series that began earlier this summer. The build pairs with Android Gradle Plugin 9.4.0-alpha08 and focuses on stability, with a batch of fixed issues spanning the AI agent, the profilers, and core IDE infrastructure. For Flutter developers running the Canary channel, the update is available through Help > Check for Updates, or Android Studio > Check for Updates on macOS, while new users can download it from the preview page.

Quail 4 is shaping up to be the release where Android Studio's agentic tooling matures into a dependable part of the daily workflow. Canary builds exist precisely to surface rough edges, and this cycle's changelog shows the team responding to exactly the kind of feedback that only real-world usage produces. The fixed issues in Canary 4 are a mix of long-standing annoyances and freshly reported regressions, all of which matter to anyone who lives in the IDE all day.

Critical AI Agent Fixes Land in This Build

The most significant fix in Canary 4 addresses a critical data-loss issue in the AI agent. Issue #540709807 describes a scenario where the agent executed a malformed shell command that deleted drive contents, a worst-case outcome for any developer relying on agentic assistance. The fix prevents the agent from running malformed shell commands in a way that can cause this kind of damage, and it should give users more confidence when delegating file operations and build commands to the assistant.

Alongside that critical fix, the release resolves two other Gemini-related problems. The AI grep tool call, which repeatedly failed to execute, now works as intended, restoring a frequently used codebase search path for agent-driven workflows. The second fix restores shell command availability in the sandbox of the Gemini in Android Studio experience, meaning agents can once again run commands in the isolated environment where they test their actions.

These fixes matter for Flutter developers because agentic tooling is becoming a normal part of Android and Flutter development alike. When an agent can reliably grep a codebase, run builds, and resolve issues without dangerous side effects, it stops being a novelty and becomes a genuine productivity tool. The Canary 4 changelog suggests Google is treating agent reliability as a first-class concern, not an afterthought.

Profilers and Core IDE Fixes

Outside the AI features, Canary 4 tackles several long-standing quality-of-life issues. The profiler, a tool Flutter developers rely on heavily for performance work, gets a fix for tiny fonts in the CPU and native memory charts. Anyone who has squinted at profiler labels on a high-resolution display will appreciate this one, as the charts are central to diagnosing frame drops and memory growth in Flutter apps.

The release also fixes a memory leak in a core tools file, the SparseArray implementation, which had been accumulating memory over long IDE sessions. For developers who keep Android Studio open for days at a time, this addresses a slow but real degradation in responsiveness.

• Critical agent fix: prevents malformed shell commands from causing data loss
• Gemini tools restored: AI grep tool calls and sandbox shell commands work again
• Profiler polish: tiny fonts in CPU and native memory charts are fixed
• Memory leak resolved: SparseArray no longer leaks memory over long sessions

One quirk in the changelog is a Hangouts regression fix, addressing a Chrome crash on screen sharing through Hangouts. It is a reminder that the Android Studio team maintains a broad surface area, and that some fixes land for reasons that have little to do with mobile development directly.

For developers tracking the Quail 4 feature set, the preview release notes remain the definitive source for what is new beyond the bug fixes. The Canary channel continues to be the place where the next generation of Android Studio features takes shape, and each new build narrows the gap between preview and stable.

The Android Gradle Plugin 9.4.0-alpha08 pairing is worth noting for Flutter teams managing native Android integrations. With AGP 9's transition to built-in Kotlin and the ongoing version-matrix changes that Flutter's own release notes document, staying on a recent Canary build helps teams verify compatibility early rather than discovering issues after the stable release lands.

As always, Google encourages users to report bugs encountered in Canary builds, and to vote for existing issues to signal impact. The fixed-issues lists in each Canary release are built directly from those reports, making the community an active participant in shaping what reaches the stable channel.

For Flutter developers, the takeaway from Quail 4 Canary 4 is straightforward: the agentic tooling is getting safer and more reliable, the profiler is becoming more usable, and the IDE infrastructure is being hardened for long sessions. It is a solid incremental step in the march toward the Quail 4 stable release, and a good reason to keep an eye on the preview channel.