Follow-up to the cherry-picked #116014: - Pin per the dependency policy (pre-1.0: `<0.(minor+2)`): httptools `>=0.6.3,<0.9` (floor = uvicorn[standard]'s own floor), uvloop `>=0.15.1,<0.24`. `watchfiles>=0.20,<2` already complied. - Copy uvicorn's own uvloop marker (win32, cygwin, PyPy) plus `sys_platform != 'android'` so `pip install '.[all]'` on those hosts does not fail on the extra either. - `tools/lazy_deps.py` mirrors the `web` extra for the lazy dashboard install: it also requested `uvicorn[standard]`, so a Termux user opening the dashboard would have hit the same uvloop build at first use. The web_server install hint follows. - `uv lock` regenerated; the lock delta is exactly the pyproject delta. - Two invariant tests: no Termux-reachable extra (or core, or the lazy dashboard feature) requests uvloop; `[all]` still does, off Android. - Docs: troubleshooting entry in the Termux guide.
4.9 KiB
sidebar_position, title, description
| sidebar_position | title | description |
|---|---|---|
| 3 | Android / Termux | Install Hermes Agent on Android from its signed Termux APT repository |
Hermes on Android with Termux
The Termux package runs Hermes on aarch64 (arm64-v8a) Android devices. This package is in prerelease testing.
The package includes Python, Node.js, npm, uv, ripgrep, ffmpeg, and their runtime libraries.
CI builds the native Python wheels and the TUI before it creates the package.
The device does not compile core dependencies or assemble its base Python
environment during installation. The package uses Python 3.14 with the bionic
interpreter pin; it does not require the same patch version as desktop CPython.
The wheel closure is core plus acp, not all desktop extras.
Install
Use the standard Termux application.
The package requires its standard prefix, /data/data/com.termux/files/usr.
Other architectures and renamed Termux application packages are not supported.
The wheels target Android API 24 (android_24_arm64_v8a).
Do not use the desktop/server install.sh or a glibc Linux archive on this target.
-
Install the tools for repository setup:
pkg install curl gnupg -
Download the public key:
mkdir -p "$PREFIX/etc/apt/keyrings" curl -fsSL \ https://hermes-assets.nousresearch.com/releases/termux/canary/key.asc \ -o "$PREFIX/etc/apt/keyrings/hermes-agent.asc" -
Verify its primary fingerprint:
gpg --show-keys --with-fingerprint "$PREFIX/etc/apt/keyrings/hermes-agent.asc"The repository key fingerprint is:
C572 B5FD D1A2 9CCF A9A9 12B6 840B 0848 E139 156DIf the fingerprint differs, stop. Do not disable signature verification.
-
Add the canary repository:
printf '%s\n' \ "deb [signed-by=$PREFIX/etc/apt/keyrings/hermes-agent.asc] https://hermes-assets.nousresearch.com/releases/termux/canary hermes-canary main" \ > "$PREFIX/etc/apt/sources.list.d/hermes-agent.list" -
Install Hermes:
pkg update pkg install hermes-agent -
Configure a provider, then start the TUI:
hermes setup hermes --tui
The hermes, hermes-agent, and hermes-acp commands use the packaged runtimes.
They do not require Termux's python or nodejs packages.
Files and updates
| Contents | Location |
|---|---|
| Package files | $PREFIX/lib/hermes-agent/ |
| Command symlinks | $PREFIX/bin/hermes, $PREFIX/bin/hermes-agent, $PREFIX/bin/hermes-acp |
| Configuration and user data | ~/.hermes/, or the selected HERMES_HOME |
Update through APT:
pkg update
pkg upgrade hermes-agent
hermes update refuses to modify an APT-owned installation.
It prints the package-manager command instead.
Canary versions contain ~canary.<timestamp> and sort before the corresponding stable version.
Gateway
This APT installation does not use systemd, launchd, or Windows Scheduled Tasks. Run the gateway in a Termux session:
hermes gateway run
For a background process:
mkdir -p "${HERMES_HOME:-$HOME/.hermes}/logs"
nohup hermes gateway run >> "${HERMES_HOME:-$HOME/.hermes}/logs/gateway.log" 2>&1 &
:::warning Android process limits
Android can suspend or terminate background Termux processes.
Battery optimization exemptions and termux-wake-lock can help, but do not guarantee persistent operation.
:::
Limits
The package does not include the nemo-relay exporter. Its vendored build
toolchain does not support this target.
The package does not include Electron, local Chromium, or desktop computer-use tools. A local Docker daemon is not part of the Termux environment. Remote services have their own requirements and connectivity limits.
Phone-native Termux:API microphone and clipboard adapters are not provided by this package path. The prebuilt CLI/TUI is not proof of local voice or wake-word support. Optional integrations and third-party plugins can require dependencies that do not support Android.
Python 3.14 on this target reports sys.platform == "android". A dependency
or skill gated only to linux is not automatically available on Android.
Uninstall
pkg uninstall hermes-agent
APT removes the package and its command symlinks. It preserves your configuration, sessions, skills, and memories.
Troubleshooting
- Package not found: verify the repository entry, then run
pkg update. - Signature error: verify the public key fingerprint. Do not use an unsigned repository or bypass the error.
- Missing command: verify that
$PREFIX/binis onPATH, or reinstall the package. - Missing library or TUI bundle: report
hermes --versionand the complete error. The core package must not require a local rebuild. - Gateway stops with the screen off: review Android's battery and background-process limits.
For general diagnostics, run hermes doctor.