As the image shows, it seems hermes can't scrape js rendered pages because the usual tools are unavailable in the version of ubuntu that WSL uses. Any workarounds to this?
#Scraping js rendered pages when using WSL via windows
solemn rampart
oblique bramble
Yeah, there are workarounds. web_extract / curl only see the initial HTML, so if the site renders the content in JS, Hermes needs a browser backend rather than plain extraction.
For WSL on Windows, the best workaround is usually to bridge Hermes in WSL to Windows Chrome with Chrome DevTools MCP instead of fighting WSL’s local Chromium/Playwright deps.
From WSL:
hermes mcp add chrome-devtools-win --command cmd.exe --args /c "npx -y chrome-devtools-mcp@latest --autoConnect --no-usage-statistics"
hermes mcp test chrome-devtools-win
Then start a fresh Hermes session, or run /reload-mcp.
That lets Hermes control Windows Chrome for JS-rendered pages, which avoids the unsupported local Chromium path you’re hitting in WSL.
Fallback options are using a cloud browser backend through Browser Use / Browserbase / Nous browser tooling, or pointing Hermes at an existing Chromium/Chrome binary with AGENT_BROWSER_EXECUTABLE_PATH.
solemn rampart
Yeah, there are workarounds. `web_extract` / `curl` only see the initial HTML, s...
This is great, thank you