openclaw-android
Run OpenClaw on Android with a single command, no proot, no Linux
Runs with mockssource: GitHubKotlinMITcommit cfb0740fc096
Kotlin, MIT licensed. The project labels itself: ai, ai agent, android, homelab, low power, nodejs, openclaw and repurpose phone.
openclaw-android runs, with stand-ins for the services it depends on. An Argusic agent installed it in 10 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
OpenClaw 2026.11.3 installed globally via npm on Node.js v26.11.0; gateway starts and serves health endpoint; clawdhub v0.3.0 installed
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 10 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- openclaw --version returned 'OpenClaw 2026.11.3 (847611d)'; openclaw --dev gateway run started and curl http://localhost:19001/health returned 200 with '{"ok":true,"status":"live"}'
- Model tokens used
- 110,183
- Exact commit tested
- cfb0740fc096
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**clawdhub**: Installed and works (v0.3.0)
Note: The repository is specifically for Android/Termux (openclaw-android). The actual OpenClaw sof…
tokens used
110,183
The verify-compat.sh is specifically for Android/Termux glibc compatibility testing. It won't work …
Now I have enough data to write the final report. Let me compile my observations.
Final summary:
**Install**: npm install -g openclaw@latest succeeded (361 packages, no errors)
**Launch**: openclaw --version returns "OpenClaw 2026.11.3 (847611d)"
**Gateway**: Started successfully, health endpoint returned `{"ok":true,"status":"live"}` (HTTP 200)
**clawdhub**: Installed and works (v0.3.0)
Note: The repository is specifically for Android/Termux (openclaw-android). The actual OpenClaw sof…Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 10 minutes to install, slower than the median of the 234 comparable projects Argusic has measured.
Of the 235 ai projects Argusic has installed and timed, openclaw-android was the 167th fastest to reach a running state, and 167 of 235 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.06 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.08 |
Topics (from GitHub)
aiai-agentandroidhomelablow-powernodejsopenclawrepurpose-phoneself-hostedtermux
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openclaw-android)Questions
- Does openclaw-android run?
- openclaw-android runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 10 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test openclaw-android?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cfb0740fc096. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test openclaw-android?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does openclaw-android take to install?
- 10 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does openclaw-android need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing openclaw-android?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does openclaw-android compare with the alternatives?
- Of the 235 ai projects Argusic has installed and timed, openclaw-android was the 167th fastest to reach a running state, and 167 of 235 reached one at all.
- Where is the evidence for openclaw-android?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.