Index / DroidClaw · updated Aug 17, 2026
DroidClaw
unitedbyai/droidclaw · healthy · rank 23 of 43 by stars
Turns old Android phones into LLM-powered agents that tap and type through apps via ADB, no API keys required. Recently shipped v0.5.3 with fixed device-web session sync and QStash scheduling.
Facts
Repository
Runtime
Posture
Security breakdown
Composite 50 / 100 · how these are scored
higher is safer
higher is safer
higher is safer
higher is safer
higher is riskier
Model access
Read from the repository, not written by a model · 29 files examined
3 providers · runs locally · gateway support
Pinned models
llama-3.3-70b-versatile released 2024-12-06 — 21 months old (from the public model catalogue)
Pin last edited 6 months ago
Several defaults are pinned; the project picks one per provider rather than shipping a single default.
Evidence
Decision
Why choose DroidClaw over OpenClaw?
Why choose this
- Direct control of Android apps via accessibility/ADB without API integrations
- Repurposes idle hardware (old phones) as agents
- Plain-English goals executed as tap/type/swipe sequences
Tradeoffs
- Lacks cross-platform support (desktop/OS-wide) that OpenClaw has
- No plugin/skill ecosystem like OpenClaw's ClawHub
- Less mature multi-channel communication (e.g., Slack, voice)
Best fit
- Repurposing old Android devices as autonomous agents
- Non-technical users wanting app automation via plain English
- Tasks requiring UI interaction without APIs
Avoid if
- Need strict security sandboxing
- Require multi-user cloud deployment
- Want deep OpenClaw plugin ecosystem
README and commit history indicate active development, but community sentiment is inferred from absence of direct mentions; security and privacy practices are not detailed.
AI layer reviewed Aug 2, 2026 · how this is written
Star activity
1,561 stars today
Overview
DroidClaw is an AI agent framework that transforms Android devices—particularly older phones—into autonomous agents capable of executing high-level goals expressed in natural language. Its core architecture implements a perception → reasoning → action loop: it dumps the accessibility tree via ADB, parses interactive UI elements, diffs screen changes, and optionally captures screenshots, then leverages an LLM to decide taps, types, and swipes until the objective is met or step limit reached.
Unlike OpenClaw, which is a cross-platform personal assistant with a growing plugin ecosystem and multi-channel communication, DroidClaw focuses exclusively on device-level UI automation without requiring API keys or custom integrations. Recent commits show active maintenance: fixes for session mapping between device and web dashboard, idempotent database migrations, and QStash scheduling support indicate a maturing server component alongside the Android APK.
The project’s unique value lies in its ability to delegate tasks to existing apps (e.g., ChatGPT, Gemini, Google Search) by simulating human interaction, effectively turning any installed app into a tool for the agent. This makes it ideal for repurposing hardware, though it sacrifices the broad platform support and extensibility that OpenClaw provides.