Android Studio and Qt push AI coding deeper into the IDE

The latest AI coding story is less about one new model and more about where the work happens: inside the development environment, with specialist instructions and a reviewable execution loop. Two announcements on September 1 make that shift unusually clear.

Android Studio Quail 4 is now stable. Google says the release bundles 23 Android skills: modular instructions that are optimized for workflows such as AGP upgrades, profiling, Navigation 3, and adaptive layouts. The IDE analyzes a prompt against installed skill metadata and invokes relevant skills automatically. That is a meaningful change in the role of documentation: instead of hoping a general model remembers the right Android migration details, the environment can supply a focused procedure at the moment it is needed.

Quail 4 also adds native Gemma 4 integration for local coding assistance. Google says the smallest models can run on machines with 12 GB of RAM, while 32 GB or more is recommended for the best experience. The company describes multi-file refactoring with Gemma 4 as an offline workflow, with source code staying on the local machine and no token quota for those local requests. Those are useful options for developers balancing privacy, connectivity, and cost, although local execution still comes with a hardware and quality trade-off that each team must measure.

Qt is making a parallel move from the other direction. In its September 1 announcement, Qt says the Qt AI Assistant will stop being delivered with Qt Creator after September 30, 2026, and technical support will end on December 31. The company is redirecting that investment toward Qt-specific MCP services and agent skills, while Qt Creator 20’s ACP Client can connect agents including Claude Code, Codex, Qwen Code, and GitHub Copilot. Qt’s MCP Server extension exposes IDE state and actions to those agents.

The common thread is not that every developer should turn on maximum autonomy. It is that a useful coding assistant increasingly needs three things: access to the project’s real context, domain-specific guidance, and a visible way to inspect the changes it makes. For learners, the practical takeaway is simple: when comparing tools, look past the chat panel. Ask what knowledge the agent can load, what actions it can take, and how clearly it shows the diff, tests, and remaining uncertainty before you accept the result.