Anthropic Has Packaged Android App Testing for Claude Code but Kept It Disabled
The packaged workflow would let Claude run Android apps, move through screens, and capture evidence in emulators. Anthropic has not said when it will turn the capability on.
Listen to this story
The audio brief
Story brief
3 key pointsAnthropic’s Claude Code packages contain a near-complete Android app-testing workflow for Claude Desktop on Windows, but the company has not enabled it. Version 1.44121.4 can detect Android Studio, SDK components, ADB, system images, and virtual devices; launch an emulator; operate apps; and capture screenshots or recordings. Each emulator requires consent, organizations can disable the tools, and physical Android...
- 01
The hidden workflow appears in Claude Desktop 1.44121.4 under Settings → Claude Code → Mobile simulators.
- 02
Claude can tap coordinates, enter text, use Android navigation controls, and capture screenshots or recordings.
- 03
The setup can boot configured virtual devices after checking Android Studio, SDK, ADB, platform tools, and system images.
Claude Code appears prepared to test Android apps from inside Claude Desktop on Windows. Package evidence shows a workflow that can start an emulator, operate an app through taps and text entry, and collect screenshots or recordings—but Anthropic has kept the feature behind an activation gate.
The unreleased option appears in Claude Desktop version 1.44121.4 under Settings, then Claude Code, then Mobile simulators. It is shown only when the app receives a supported Android-emulator capability status. The same package includes an error stating that the Android Emulator is currently disabled, leaving Anthropic in control of access after the software reached production packages.
A local test environment, wired into the desktop app
The setup checks for Android Studio, the Android software-development kit, Android Debug Bridge, platform tools, system images, and configured Android Virtual Devices. If a configured emulator is shut down, the flow can boot it. Those checks assemble the local tools needed to run a simulated Android device before Claude inspects an app.
- Select, attach to, or detach from an emulator.
- Capture screenshots and recordings of an app running in the emulator.
- Drive the interface with coordinate taps, text entry, and Android Home, Back, and Recents controls.
Consent and device limits define the boundary
The design asks for consent separately for each emulator. The prompt explains that Claude will view the device through screenshots and control it by tapping and typing. Managed organizations can disable the emulator tools, while connected physical Android devices are explicitly unsupported.
The narrower simulated-device approach sits beside Anthropic’s existing computer-use feature in Claude Code and Cowork on Windows and macOS. Anthropic says computer use can click, type, and open apps after permission, and cautions that its safeguards are not perfect when Claude sees screen content and interacts with desktop software.
Android is not yet on the public product surface
Anthropic’s public documentation described iOS Simulator support but had no matching Android Emulator entry when the package was examined. The Android path instead centers on its own local toolchain: Android Studio, the SDK, ADB, system images, and virtual devices.
The package examination on September 3 established that the software was wired into the examined builds, not that it had been released. The decision that matters to developers—when Anthropic will enable the capability—remains unresolved.
Sources
- support.claude.comLet Claude use your computer in Cowork | Anthropic Help Center