Production packages include Android Studio setup, ADB controls, screenshots, recordings and device permissions, while public docs remain iOS-only.
By Ryan Merket · Published
RUNTIMEWIRE INVESTIGATION — Scoop
Original reporting by RuntimeWire, based on reverse engineering.
Why it matters #
Direct Android testing would let Claude Code inspect and operate the apps it edits, extending automated verification to a larger mobile developer base and to Windows machines.
Reporting record #
Finding
Anthropic has already built the first-party Android Emulator integration into Claude Desktop, including the Windows UI, setup flow, device controls and permission system, and is holding it behind an explicit rollout capability.
How we verified
Methods: reverse engineering.
The current 1.44121.4 UI bundle contains a Settings → Claude Code → Mobile simulators section with an Android-specific toggle: Android Emulator and this exact Windows/non-Mac description: “Let Claude verify your changes in Android emulators on this computer: running your app, driving it through flows, and capturing screenshots and recordings.” The UI only renders when this capability reports: androidEmulator.status === "supported" There is also an explicit disabled-rollout error: android_rollout_disabled → Claude Code Android Emulator is currently disabled.
Reverse engineered the latest Claude for Windows desktop app
Tested versions: 1.44121.4.
Reproduction
RuntimeWire partially reproduced the finding.
Used the assets and code to recreate the UI without modifying the code
File hashes
8d1e570bb798ada436f22dfc637be3577b335aaa1d4552356681d4808241c013 app.asar
2e60e98f31c1c3c2eb9396d3ff546ef45cf949f52c129a516fa22c21fd8165a4 claude-1.44121.4-ion-dist.zip
Company response
RuntimeWire requested comment; the company had not responded by publication time.
Anthropic has built a first-party Android Emulator integration into Claude Code Desktop and wired it into production packages, though access remains controlled by a capability and rollout gate.
The current Claude Desktop UI bundle, version v1.44121.4 dated September 3rd, contains a Mobile simulators section under Settings > Claude Code. Its Android toggle tells users: "Let Claude verify your changes in Android emulators on this computer: running your app, driving it through flows, and capturing screenshots and recordings."
That setting appears only when the application receives an androidEmulator.status
value of supported
. The package also contains a distinct android_rollout_disabled
error, paired with the message "Claude Code Android Emulator is currently disabled." The combination gives Anthropic server-side control over which accounts, organizations or installations can see and use the integration.
The code does not establish when Anthropic will turn it on. It does establish that Android support has progressed beyond a placeholder. Anthropic has packaged the interface, setup flow, host components, device controls and permission system needed to let Claude run and inspect Android apps directly.
A complete device-control stack
The integration checks for Android Studio, the Android SDK and adb
, then locates platform tools, system images and configured Android Virtual Devices. If it finds an emulator that is shut down, Claude Desktop can boot it automatically. A setup wizard handles machines without a working emulator configuration.
Once connected, Claude can attach to and detach from an emulator, capture screenshots and recordings, tap coordinates, type text and invoke Android's Home, Back and Recents controls. Those capabilities would let Claude Code move through an app's interface after changing its source, observe the result and continue editing when the app behaves incorrectly.
Each emulator carries its own consent step. The permission dialog asks, "Let Claude use this emulator?" and explains that Claude will view the screen through screenshots and control it by tapping and typing. Anthropic also included organization-level disablement, giving administrators a way to block the tools across managed installations.
Physical Android devices are excluded. Claude Desktop checks the device type and returns explicit copy when a connected target is real hardware: "'{udid}' is not an Android emulator. Physical devices are not supported." Restricting access to virtual devices narrows the blast radius of an agent that can see a screen, enter text and operate system controls.
The Android host machinery already appears in an accompanying Electron app.asar
package that identifies itself as version v1.40609.1. Anthropic appears to update the desktop UI bundle and Electron host on separate tracks, so the integration cannot be described as newly added in version v1.44121.4. The defensible timing is narrower: the feature was fully wired into production packages examined on September 3rd and remained rollout-gated.
The iOS template, rebuilt for Android
Anthropic established the product pattern in July. During the week of July 20th, Claude Code Desktop added an iOS Simulator pane that lets Claude build, launch and inspect an iOS app while streaming the simulated device beside the conversation.
Anthropic's current iOS Simulator documentation describes direct simulator control rather than general desktop automation. Claude can install an app, tap through flows, read the screen and verify changes without taking over the user's mouse or requesting the broader operating-system permissions required by computer use. Access is granted per simulated device, while managed organizations can disable Claude's simulator tools.
The unreleased Android implementation follows the same structure: direct device controls, per-emulator consent, setup checks, capture tools and administrative policy. Android adds a different toolchain centered on Android Studio, SDK system images, AVDs and adb
. It also creates a route to native mobile verification on Windows, where Apple's simulator cannot run.
Anthropic's public documentation currently contains a dedicated iOS Simulator section and no equivalent Android Emulator entry. Its documentation index likewise lists iOS simulator support without an Android counterpart.
Android support itself has been expected. A July 22nd community digest reported that an Anthropic team member said it was "coming soon" after the iOS launch. The production packages now show what that promise entails: a first-party integration with its own user interface and native host path, held behind an explicit rollout decision.
The feature extends a core competition among coding agents: closing the gap between generating code and checking whether the resulting product works. Web agents can already open browser previews, inspect page structure and click through flows. Native mobile apps require heavier local toolchains and simulated devices, leaving developers to perform much of the final verification themselves.
Anthropic's Android integration gives Claude the machinery to run that loop inside Claude Code Desktop. A rollout gate leaves the launch date, eligible plans and initial platform coverage under Anthropic's control.
RuntimeWire reached out to Anthropic for comment and will update this story if the company responds.