mirrors/hermes-agent
1
0
Fork 0
mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-05-08 03:01:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

docs(browser): document WSL-to-Windows Chrome MCP bridge

Browse source
This commit is contained in:
liuyuqi 2026-04-12 18:34:13 +08:00 • committed by Teknium
parent a860a1098f
commit a11234dd68
3 changed files with 109 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
website/docs/reference/faq.md
View file

@ -36,6 +36,24 @@ Set your provider with `hermes model` or by editing `~/.hermes/.env`. See the [E
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
```
### I run Hermes in WSL2. What's the best way to control my normal Windows Chrome?
Prefer an MCP bridge over `/browser connect`.
Recommended pattern:
- run Hermes inside WSL2
- keep using your normal signed-in Chrome on Windows
- add `chrome-devtools-mcp` as an MCP server through `cmd.exe` or `powershell.exe`
- let Hermes use the resulting MCP browser tools
This is more reliable than trying to force Hermes core browser transport to attach directly across the WSL2/Windows boundary.
See:
- [Use MCP with Hermes](../guides/use-mcp-with-hermes.md#wsl2-bridge-hermes-in-wsl-to-windows-chrome)
- [Browser Automation](../user-guide/features/browser.md#wsl2--windows-chrome-prefer-mcp-over-browser-connect)
### Does it work on Android / Termux?
Yes — Hermes now has a tested Termux install path for Android phones.