Feature
Hermes Agent Browser Automation: Browser Use, Cloud Browsers, and Local Chrome
Quick answer
Current Hermes browser automation defaults to Browser Use mode when Browser Use CLI 3.0 and terminal access are available. Check it with `/browser use status`; use named `browser_exec` sessions for concurrent work or `/browser use off` to force the built-in tools. Then choose a browser source such as local Chrome, Lightpanda, Nous Tool Gateway, Browserbase, Firecrawl, or Camofox, and verify every task with URLs, screenshots, console output, and real final state.
Key Points
- ✓Browser Use CLI 3.0 is the default driver when runnable, exposing one browser_exec tool for model-written browser Python
- ✓Named browser_exec sessions isolate parallel agents and simultaneous chats instead of sharing one browser connection
- ✓Browser sources include Nous Tool Gateway, Browserbase, Browser Use cloud, Firecrawl, Camofox, Lightpanda, local Chromium, and your own Chromium-family browser over CDP
- ✓Lightpanda provides a fast, low-memory local engine with automatic Chrome fallback for unsupported actions
- ✓Built-in accessibility snapshots, screenshots, vision, and console inspection remain available when Browser Use mode is off or unavailable
- ✓Hybrid routing keeps localhost and LAN URLs local while public URLs use the configured cloud source
- ✓Browser sessions are credential-bearing state: gate purchases, messages, uploads, account changes, and destructive actions
- ✓Use extraction or APIs for simple retrieval; reserve a browser for rendered JavaScript, auth, forms, layout, and interaction
How It Works
- 1Run hermes tools, enable Browser Automation, and choose the browser source; Browser Use mode becomes the default driver when its CLI is runnable
- 2Use /browser use status to inspect the driver, /browser use off to force built-in tools, and explicit browser_exec session names for concurrent work
- 3For your own Chrome, Brave, Chromium, or Edge session, start Hermes in the terminal and run /browser connect; gateway chats do not execute this CLI command
- 4Give Hermes a URL, viewport, allowed actions, success conditions, and evidence requirements
- 5Verify final URL, visible state, screenshots, console errors, and the real business outcome before reporting success
Real-World Use Cases
Rendered Website and Funnel QA
Open the production page at desktop and phone widths, click the real CTA, check redirects and attribution parameters, inspect console errors, capture screenshots, and verify the final state instead of treating HTTP 200 as success.
Authenticated Dashboard Work
Attach a dedicated local Chromium-family profile or use profile-scoped Camofox persistence for workflows that need approved login state. Keep browser profiles private and separate read-only inspection from side-effecting actions.
Local Development plus Public Research
With a cloud provider configured, Hermes can automatically route localhost, loopback, LAN, and internal URLs to a local Chromium sidecar while public URLs remain in the cloud session. The cloud provider never receives the private URL.
Scheduled Visual Monitoring
Pair browser checks with Hermes cron and explicit Telegram, Discord, or Slack delivery. Alert on meaningful changes or broken outcomes, and include the tested URL, viewport, screenshot, console summary, and failing layer.
Separate driver from browser source
First identify Browser Use mode versus built-in tools, then identify the local or cloud browser source. This prevents a browser_exec or terminal-access problem from being misdiagnosed as a Browserbase, Firecrawl, or CDP outage.
Hybrid routing protects private URLs
A configured cloud provider does not have to block local development. Hermes can route localhost, loopback, LAN, .local, .lan, and .internal targets to a local sidecar while public URLs stay in the cloud. Redirects from public URLs into private space remain blocked.
/browser connect is CLI-only
Run /browser connect from an interactive terminal session to attach Chrome, Brave, Chromium, or Edge over CDP. Sending the same text in Web UI, Telegram, Discord, or another gateway does not establish the connection; gateway chats pass it to the agent as ordinary text.
Success means evidence, not clicks
A good browser run reports the tested URL and viewport, actions taken, final URL and visible state, console errors, screenshot path, and exact blocker. Purchases, submissions, messages, account changes, uploads, and destructive admin actions need explicit authorization.
Under the Hood
Hermes browser automation has two layers. The driver is Browser Use mode (`browser_exec`) or the built-in snapshot/click/type toolset. The browser source is local Chrome, Nous Tool Gateway, Browserbase, Browser Use cloud, Firecrawl, Camofox, Lightpanda, or local Chromium. Browser Use mode is selected automatically when `browser.backend` is unset and its CLI is runnable. It requires terminal access because the tool executes model-written Python locally; locked-down sessions retain the built-in tools.
Named `browser_exec` sessions isolate the harness daemon, IPC state, logs, and cloud browser. Use them for parallel subagents or simultaneous chats. The unnamed default session is appropriate for serial work. `/browser use status` identifies the effective mode; `/browser use off` forces the built-in tools for comparison or troubleshooting.
Lightpanda adds a machine-first local engine with fast startup and lower memory use than Chromium. Hermes falls back to Chrome for actions Lightpanda cannot complete. Backend choice changes where the browser runs, not the success contract: require final URLs, visible state, screenshots, console evidence, and real artifacts.
Hybrid routing keeps private and loopback addresses on a local sidecar while public URLs use the selected cloud source. Treat persistent browser state as a credential, isolate profiles, and gate all side effects.
Frequently asked questions
Which browser backends does Hermes Agent support?
Hermes supports Nous Tool Gateway, Browserbase, Browser Use cloud, Firecrawl, Camofox, Lightpanda, local Chromium through agent-browser, and Chrome, Brave, Chromium, or Edge over CDP. Browser Use CLI 3.0 is the default driver when runnable; otherwise Hermes uses the built-in tools.
What is Browser Use mode in Hermes?
It is the current default browser driver when Browser Use CLI 3.0 can run. Hermes exposes one browser_exec tool that executes model-written Python and can drive local or cloud browser sources. Use /browser use status to inspect it and /browser use off to force built-in tools.
Can browser_exec isolate parallel browser tasks?
Yes. Pass a unique session name for each parallel agent or chat. Every name gets separate harness state and, on cloud sources, a separate browser. Omitting the name uses the shared default session.
Is Hermes browser automation the same as Playwright?
No. Hermes provides an agent-facing browser toolset with accessibility snapshots, element references, screenshots, vision, and console inspection across several backends. It can perform Playwright-style QA tasks, but deterministic CI tests should remain in a formal browser-test suite when exact reproducibility is required.
How do I connect Hermes to my own Chrome or Brave browser?
Start Hermes in an interactive terminal and run /browser connect. Hermes can auto-launch or attach to a Chromium-family browser over CDP. The command is CLI-only and does not execute from Web UI or messaging gateways.
Can a cloud browser test localhost?
Yes, through Hermes hybrid routing. Private and loopback targets use a local Chromium sidecar by default while public targets use the configured cloud provider, so the cloud browser never receives your private URL.
Can Hermes keep browser logins between tasks?
Camofox can use profile-scoped managed persistence when browser.camofox.managed_persistence is set and the server supports stable user-ID profiles. CDP can also attach to an approved dedicated browser profile. Treat either as sensitive credential-bearing state.
When should I avoid browser automation?
Use web search, web extraction, RSS, an API, or MCP when you only need text or structured data. Use a browser when JavaScript rendering, authentication, clicks, forms, dialogs, layout, screenshots, or console behavior changes the answer.
How should Hermes handle CAPTCHA and protected flows?
Use only authorized provider capabilities and account access. If a challenge requires a person or access is denied, pause for human input or report the blocker; never guess that the protected action succeeded or bypass a site's rules.
Should I self-host browser automation or use FlyHermes?
Self-host when local profiles, private networks, custom browser infrastructure, and runtime control are the goal. Use FlyHermes when you want managed browser and phone access, connected channels, and uptime without operating the VPS, browser service, gateway, and provider stack yourself.
Next setup steps
Browser automation setup
Configure a cloud provider, Camofox, local Chromium, or a live Chrome/Brave CDP session and run an evidence-backed smoke test.
Browser automation operations guide
Use copy-paste QA contracts, logged-in session boundaries, screenshots, and console evidence in real workflows.
Hermes dashboard and Web UI
Monitor the profile, provider, sessions, cron jobs, tools, logs, and gateway surrounding a browser workflow.
AI agent monitoring
Define trigger-to-delivery success contracts for browser checks and other unattended agent work.
Hermes cron jobs
Schedule stable visual checks with pinned profiles, models, workdirs, and delivery targets.