Run Hermes on Android with Termux

Termux can host a useful phone-native Hermes CLI, but Android is a Tier 2 platform and the tested dependency set is intentionally narrower than desktop or server installs. Treat mobile support as a focused runtime, not a promise that every optional extra will work.

Official documentation: https://hermes-agent.nousresearch.com/docs/getting-started/termux

Use the Termux-aware path

The official installer detects Termux and selects the compatible bundle. If manual recovery is required, use a standard Python virtual environment, set ANDROID_API_LEVEL, and install the documented Termux constraints. Do not substitute the full .[all] extra when the Android guide specifies .[termux].

Design around phone constraints

Core chat and supported tools can work well on a phone. Voice dependencies and some browser or WhatsApp tooling may remain unsupported or experimental. Keep long-running jobs aware of Android background-process limits, battery use, network changes, and storage permissions.

Operational checklist

Install the current Termux app from a trusted source.
Update Termux packages before installing Hermes.
Use the official one-line installer first.
Keep the manual constrained install as the recovery path.
Verify hermes version and hermes doctor.
Test one provider and one harmless local task.
Document unsupported extras before relying on them.

Common pitfalls

Installing .[all] and hitting unsupported voice packages.
Using uv pip install when the guide specifies stdlib venv plus pip.
Forgetting ANDROID_API_LEVEL during Rust-backed package builds.
Assuming desktop audio and browser behavior on Android.
Leaving secrets in shared storage or screenshots.

Verification steps

Open a new Termux session and run hermes version.
Run hermes doctor.
Complete one text conversation.
Confirm required commands such as git, node, ripgrep, and ffmpeg resolve when needed.
Restart Termux and verify the hermes command remains on PATH.

A reliable Hermes workflow is defined by observable behavior, bounded authority, and repeatable verification—not by configuration alone.