From a9a0e2da070edc1d2657f58cdd2ef962658a046e Mon Sep 17 00:00:00 2001 From: "Zak B. Elep" Date: Mon, 10 Aug 2026 17:47:41 +0800 Subject: [PATCH] docs(termux): correct browser prerequisites for local vs cloud mode 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. --- website/docs/getting-started/termux.md | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/website/docs/getting-started/termux.md b/website/docs/getting-started/termux.md index fe84c3f77c..1545ff6445 100644 --- a/website/docs/getting-started/termux.md +++ b/website/docs/getting-started/termux.md @@ -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.