How to Install Openclaw in Termux

Running OpenClaw Locally on Android: The Bionic Bypass

OpenClaw is typically deployed on high-end desktop environments or cloud servers. This walkthrough demonstrates how to run the complete OpenClaw stack—including Gateway, Browser Control, and WhatsApp/Telegram integrations—directly on an Android device using Termux.

---

Prerequisites & Requirements

• Android Device: Running Android 10 or newer.
• Termux: Installed from F-Droid (Google Play Store builds are deprecated and not supported).
• Gemini API Access: Obtain a free API key from Google AI Studio.

---

1. Environment Preparation (Ubuntu PRoot)

OpenClaw depends on native Linux components that do not perform reliably in standard Termux user space. To prevent these incompatibilities, we create an isolated Ubuntu container using proot-distro.

pkg update && pkg upgrade -y
pkg install proot-distro -y

proot-distro install ubuntu
proot-distro login ubuntu

---

2. Dependency & OpenClaw Installation

Inside the Ubuntu environment, install Node.js 22 along with the required build essentials, then install OpenClaw globally via npm:

apt update && apt upgrade -y
apt install curl git build-essential -y

curl -fsSL https://deb.nodesource.com/setup_22.x | bash -
apt install -y nodejs

npm install -g openclaw@latest

---

3. Applying the "Bionic Bypass" (Mandatory Step)

Android’s kernel restrictions block access to os.networkInterfaces(), throwing a System Error 13 when Node applications attempt to query network interfaces. We bypass this by creating a lightweight hook script that patches Node.js prior to OpenClaw's execution.

Create the Override Script

cat << 'EOF' > /root/hijack.js
const os = require('os');
os.networkInterfaces = () => ({});
EOF

Apply It Globally via Shell Profile

echo 'export NODE_OPTIONS="-r /root/hijack.js"' >> ~/.bashrc
source ~/.bashrc

---

4. Initial Configuration Wizard

Because OpenClaw is installed globally, you can initiate the onboarding configuration wizard from any working directory:

openclaw onboard

CRITICAL WARNING: When prompted to configure the Gateway Bind setting, select 127.0.0.1 (Loopback). Selecting 0.0.0.0 or a LAN IP address will cause the gateway to crash on non-rooted Android devices.

---

5. Launching the Gateway

Start the OpenClaw gateway with verbose logging enabled to inspect active connections:

openclaw gateway --verbose

Available Chat Commands

Once linked with messaging integrations (such as WhatsApp or Telegram), the following chat commands can be issued directly in conversations:

• /status — Display current gateway health and active sessions.
• /think high — Enable enhanced reasoning and deep reflection mode.
• /reset — Reset the current conversation context state.

---

Tips, Web Dashboard & Troubleshooting

• Web Dashboard Access: Open http://127.0.0.1:18789 in your mobile browser. You can retrieve your gateway access token anytime with:

  openclaw config get gateway.auth.token

• Prevent Background Termination: Run termux-wake-lock in a separate Termux tab and turn off Battery Optimization for Termux in your Android device settings.
• Security Reminder: Keep API keys and gateway tokens secure. Revoke any keys used during initial setups or video demonstrations.