Summary

Andclaw enables AI agents to control Android phones entirely on-device, automating tasks without root or PC connections. It targets users seeking mobile automation, developers, and enterprise device management, offering sophisticated interaction and control. The key benefit is powerful mobile AI automation with minimal setup and zero external dependencies for core functions.

How It Works

Andclaw uses Android's Accessibility Services, eliminating root, ADB, or Shizuku needs. It analyzes UI accessibility node trees and supplements with automatic screenshots for visual analysis, especially in web contexts. Supporting Kimi Code, Moonshot, and OpenAI-compatible APIs, it facilitates nuanced, human-like interactions (clicks, swipes, text input) and prioritizes on-device operation.

Quick Start & Requirements

• Environment: Android 12 (API 31) or higher.
• Permissions: Manual enabling of Accessibility Service and Floating Window permissions.
• Installation: Via Chrome browser (andclaw.app/#/install) or build from source (git clone ..., ./gradlew :app:installDebug).
• Prerequisites: API key from Kimi Code, Moonshot, or OpenAI-compatible provider.
• Device Owner Activation (Optional): Requires ADB and factory reset (adb shell dpm set-device-owner com.andforce.andclaw/.DeviceAdminReceiver) for advanced features.
• Remote Control: Setup via Telegram Bot (BotFather) and entering Bot Token.

Highlighted Details

• AI Model Support: Integrates Kimi Code, Moonshot, and OpenAI-compatible APIs, supporting multimodal input (text + screenshots).
• Remote Control: Full device control, status queries, and media retrieval (screenshots, recordings) via Telegram Bot.
• Device Owner Capabilities: Enables silent app management, device control, and Kiosk mode.
• Robust Operation: Features loop detection and automatic screenshot retries.

Maintenance & Community

Maintained by the "Andclaw Team." A WeChat group is available for community interaction.

Licensing & Compatibility

Released under the permissive MIT License, allowing commercial use and integration into closed-source projects.

Limitations & Caveats

Requires Android 12+. Full device management depends on Device Owner activation (factory reset + ADB). Users must be aware screen data is sent to LLM providers, raising privacy considerations.