Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/openagen/zeroclaw/llms.txt

Use this file to discover all available pages before exploring further.

ZeroClaw provides prebuilt binaries for Android devices targeting both modern 64-bit phones and older 32-bit hardware. The recommended path is Termux, which gives you a full Linux-like environment without requiring root.

​
Supported architectures

TargetAndroid versionDevices
aarch64-linux-androidAndroid 5.0+ (API 21+)Modern 64-bit phones
armv7-linux-androideabiAndroid 4.1+ (API 16+)Older 32-bit phones (Galaxy S3, etc.)

​
Installation via Termux

1

Install Termux

Download Termux from F-Droid or from the GitHub releases page.
The Play Store version of Termux is outdated and unsupported. Use F-Droid or the GitHub release.
2

Check your device architecture

Open Termux and run:
uname -m
  • aarch64 — 64-bit device, use the aarch64-linux-android binary
  • armv7l or armv8l — 32-bit device, use the armv7-linux-androideabi binary
3

Download the ZeroClaw binary

curl -LO https://github.com/zeroclaw-labs/zeroclaw/releases/latest/download/zeroclaw-aarch64-linux-android.tar.gz
tar xzf zeroclaw-aarch64-linux-android.tar.gz
4

Install and verify

chmod +x zeroclaw
mv zeroclaw $PREFIX/bin/

# Verify installation
zeroclaw --version

# Run initial setup
zeroclaw onboard

​
Direct installation via ADB

For advanced users who want to run ZeroClaw outside Termux: 
# From your computer with ADB connected
adb push zeroclaw /data/local/tmp/
adb shell chmod +x /data/local/tmp/zeroclaw
adb shell /data/local/tmp/zeroclaw --version
Running ZeroClaw outside Termux requires a rooted device or specific system permissions for full functionality.

​
Android-specific limitations

LimitationDetails
No systemdUse Termux’s termux-services package for daemon mode
Storage accessRun termux-setup-storage to grant Termux access to shared storage
Network bindingSome features may require Android VPN permission for local address binding
USB peripheral discoverynusb (USB device enumeration via VID/PID) is excluded on target_os = "android"
The nusb exclusion means zeroclaw hardware discover is not available when running on Android itself. To use USB-connected peripherals (STM32, ESP32), run ZeroClaw on a Linux or macOS host and connect to Android via ADB if needed.

​
Building from source

To cross-compile ZeroClaw for Android on a Linux or macOS host: 
# Add Android targets to your Rust toolchain
rustup target add armv7-linux-androideabi aarch64-linux-android

# Set NDK path (adjust to your NDK installation)
export ANDROID_NDK_HOME=/path/to/ndk
export PATH=$ANDROID_NDK_HOME/toolchains/llvm/prebuilt/linux-x86_64/bin:$PATH

# Build for 64-bit Android
cargo build --release --target aarch64-linux-android

# Build for 32-bit Android
cargo build --release --target armv7-linux-androideabi

​
Troubleshooting

chmod +x zeroclaw
You downloaded a binary for the wrong architecture. Run uname -m in Termux to confirm your device’s architecture, then download the matching binary.
Use the armv7-linux-androideabi build. Ensure your device is running API level 16 or higher.

Build docs developers (and LLMs) love

Get started for freeTalk to us