ouyangbo/hermes-agent
1
0
Fork 0
Code Issues Pull Requests Actions 9 Packages Projects Releases Wiki Activity

docs(termux): correct browser prerequisites for local vs cloud mode

Browse Source 
The doc claimed Node.js alone was enough for browser tooling, but
local mode on Termux rejects the bare npx fallback and needs a real
agent-browser install; only cloud browser providers work with npx
alone.
This commit is contained in:
Zak B. Elep
2026-08-10 17:47:41 +08:00
committed by Teknium
parent f4d3592b65
commit a9a0e2da07
1 changed files with 13 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/docs/getting-started/termux.md
+13 -4
View File
@@ -155,11 +155,20 @@ hermes setup
### Install optional Node dependencies manually
The tested Termux path skips Node/browser bootstrap on purpose. If you want to experiment with browser tooling later, the only prerequisite is Node.js — `agent-browser` itself resolves lazily via `npx agent-browser` on first browser-tool use, so there's no separate install step:
The tested Termux path skips Node/browser bootstrap on purpose. If you want to experiment with browser tooling later, what you need depends on which backend you use:
```bash
pkg install nodejs-lts
```
- **Cloud browser providers** (Browserbase, Browser Use, Firecrawl) host their own Chromium, so Node.js alone is enough — `agent-browser` resolves lazily via `npx agent-browser` on first use:
```bash
pkg install nodejs-lts
```
- **Local browser automation** on Termux needs a real `agent-browser` install — the bare npx fallback is deliberately rejected in local mode as too fragile to advertise as ready:
```bash
pkg install nodejs-lts
npm install -g agent-browser && agent-browser install
```
The browser tool automatically includes Termux directories (`/data/data/com.termux/files/usr/bin`) in its PATH search, so `agent-browser` and `npx` are discovered without any extra PATH configuration.