OpenClaw on Android
Run OpenClaw on Android with a single command — no proot, no Linux.
Evidence shows the install script executes remote code (curl | bash) without providing audit or checksum verification. User confirmation is present via interactive prompts (Y/n), but permission requests are not clearly explained. Data flow transparency is insufficient; no explanation of how data is collected or transmitted. Sensitive data handling is not mentioned. Dependency security relies on npm packages and external binaries without integrity checks. External effects include modifying system paths and environment variables, but not clearly stated. Rollback is provided via uninstall and backup commands, but not verified. Source attribution is unverified publisher identity.
Self-consistency is good; README and script structure align, but there are inconsistencies (e.g., README mentions 'openclaw onboard' but not verified in scripts). Dependency availability relies on external services (myopenclawhub.com) and npm without mirrors or fallbacks. Failure messages are provided via error handling and verification scripts, but not all failure scenarios are covered.
Target audience is clear (Android users), scenarios cover install, update, backup. Capability boundaries are clear with optional tools and limitations. Trigger precision is adequate for install command, but update/uninstall commands may lack precision. Environment fit supports Android 7.0+ and Termux, but not all device variants.
Information architecture is clear with README, docs, and project structure. Install notes are detailed but rely on external URLs. Naming stability is mostly stable but has version migrations. Examples and FAQ are present with troubleshooting docs. Known limitations are listed (performance, local LLM). License is MIT but copyright year 2026 may be inaccurate. Versioning/changelog is missing. Maintenance responsibility is not clearly assigned.
Output usability is provided via CLI and APK, but actual output not verified. Marginal value is clear by solving proot pain points. Cost-benefit is favorable with short install time, but relies on external services.
Claim traceability is partial; README claims not fully mapped to code. Cross-source corroboration is absent. Fact-inference separation is weak; some claims (e.g., performance) lack benchmarks.
- Install script executes from remote URL, posing supply chain risk; review script content.
- Relies on external services (myopenclawhub.com) and npm packages without integrity checks.
- No changelog provided; maintenance responsibility unclear.
What does this agent do, and when should you use it?
OpenClaw on Android is an installer and runtime that brings the OpenClaw AI agent platform to Android devices via Termux. It eliminates the 700MB-1GB overhead of traditional methods by installing only the glibc dynamic linker (not a full proot-distro Linux), enabling native performance. The project includes a one-command installer (curl | bash), a CLI management tool (oa), and a standalone Claw App APK with a built-in terminal emulator and WebView-based UI that doesn't require Termux. It automatically handles path conversion, Node.js setup, temp folder configuration, and bypasses systemd and phantom process killer restrictions. Users can start the gateway with 'openclaw gateway' and manage installations with oa --update, oa --backup, and oa --restore.
The installer automates setup: it detects the Termux environment, installs glibc-runner (providing ld-linux-aarch64.so.1), downloads Node.js v22 linux-arm64 and wraps it in an ld.so loader script, converts standard Linux paths (/tmp, /bin/sh, /usr/bin/env) to Termux paths, configures a temp folder, and bypasses systemd. It installs OpenClaw (via npm install -g openclaw@latest --ignore-scripts) to avoid postinstall compilation of llama.cpp. It also installs clawdhub (skill manager) and optional tools like tmux, ttyd, dufs, android-tools, code-server, OpenCode, Chromium, Playwright, Claude Code, Gemini CLI, and Codex CLI. After installation, users run 'openclaw onboard' to complete initial setup, then 'openclaw gateway' to start the gateway. The 'oa' command handles updates, backups (oa --backup), restores (oa --restore), status, and uninstall.
- Users wanting to repurpose an old Android phone as a low-power, always-on AI agent gateway.
- Self-hosters who want to avoid the 20-30 minute setup and 1-2GB storage overhead of traditional proot-distro methods.
- Developers needing to run code-server or AI CLI tools (e.g., Claude Code) on a mobile device.
- Users who prefer a standalone APK (Claw App) with a built-in terminal and dashboard UI, without requiring Termux.
- Users managing multiple Android devices running OpenClaw, using Dashboard Connect to access from a PC.
What are this agent's strengths and limitations?
- Avoids full Linux distro: saves ~800MB and ~20 minutes compared to proot-distro by using only the glibc dynamic linker.
- Automated installation: one command handles all compatibility (paths, Node.js, systemd bypass).
- Maintenance tooling: oa CLI enables updates, backups, restore, and uninstall, easing ongoing management.
- Android-only: requires Termux (or Claw App), limited to Android 7.0+.
- Potential background termination: Android may kill processes due to Phantom Process Killer; requires documented settings adjustments.
- Local LLM performance limited: on-device inference is slow and constrained by RAM/storage; cloud LLM APIs are recommended.
How do you install or deploy this agent?
- Install Termux from F-Droid (Play Store version is discontinued). 2. Open Termux and run: pkg update -y && pkg install -y curl. 3. Run the installer: curl -sL myopenclawhub.com/install | bash && source ~/.bashrc. Installation takes 3-10 minutes. You'll be prompted to select optional tools (tmux, code-server, etc.). Alternatively, download the Claw App APK from the Releases page and install it—no Termux required.
How do you use this agent?
After installation, run 'openclaw onboard' to complete initial setup. Then open a new terminal tab and run 'openclaw gateway' to start the gateway. Run the gateway directly in the Termux app on your phone, not via SSH. Use the 'oa' command to manage the installation: oa --update to update all components, oa --backup to create backups, oa --restore to restore from a backup, oa --status to view status. For dashboard access or SSH, refer to the Termux SSH setup guide.
How does this agent compare with similar options?
The README explicitly compares the standard proot-distro approach (full Linux distro) with this project, highlighting storage overhead (1-2GB vs ~200MB), setup time (20-30 min vs 3-10 min), and performance. No other alternatives are mentioned.