Hermes Agent · Tutorial 12
Set Up Hermes Browser Use Mode Safely
Choose a Hermes browser provider, verify Browser Use mode, protect private sessions, and test the setup on one bounded task.

0 of 1 complete
Reference guide · Read when needed · View the route
Hermes Browser Use mode gives the agent one browser_exec tool. The agent writes a short Python program that can navigate, click, type, extract data, and recover from simple failures in one run.
After this lesson you can confirm the mode is on, run one read-only extract on a public page, and reject a result that has no URL you can open.
On a current Hermes installation, Browser Use mode is the default when browser.backend is unset. The driver ships with Hermes: the docs describe browser-harness as the engine and the Browser Use CLI as a thin wrapper around it, including in the Desktop app. The browser_exec tool is offered only to sessions that also have terminal access. If the engine is missing, Hermes falls back to its built-in browser tools, and hermes update is the documented way to restore it. Camofox stays on the built-in tools, because it has no CDP endpoint for this driver.
We re-checked the official Browser Automation page on October 22, 2026. The separate browser-setup URL used in the August lesson now returns 404. Provider setup lives on that same page.

Choose the browser source
Browser Use is the driver. You still choose where the browser runs.
| Need | Start with | Trade-off |
|---|---|---|
| A clean local browser | Packaged Chromium, the default local source | Separate from your signed-in Chrome. Install it from hermes tools |
| Watch an existing local browser | Chromium-family CDP via /browser connect | Shares that machine and can expose a signed-in session |
| Browse with your current logins | Real-profile toggle, off by default | Copies cookies into a snapshot. Consent, not an isolation boundary |
| Run remotely or on a schedule | Browser Use Cloud, Browserbase, Firecrawl, or Nous Subscription | Sends page content and actions to that provider |
| A lighter local engine | Lightpanda, where the page fits | Some actions fall back to Chrome. Speed claims still need your own timing |
| Use Camofox | Built-in Hermes browser tools | Camofox has no CDP endpoint for the Browser Use driver |
Open hermes tools, select Browser Automation, and configure the provider you intend to use. Adding a provider key does not switch the provider by itself. The docs say the active choice is browser.cloud_provider, written by that menu. Once a selection exists, a new key does not silently reroute. Never-configured setups can still autodetect from available credentials.
The day-by-day version of this choice is the first-week checklist.
Verify the active mode
Start a fresh Hermes session and run:
/browser status
Confirm the browser source and whether Browser Use mode is active. Then give Hermes a read-only task with a visible success condition:
Open the official Hermes Browser Use documentation.
Return the names of the supported browser providers in a table.
Include the page URL. Do not sign in, download files, or submit forms.
The setup passes if the provider starts, Hermes returns the source URL, and the list matches the page. A confident answer without a URL is not enough.
Force Browser Use or turn it off
To force the driver in ~/.hermes/config.yaml:
browser:
backend: "browser-use"
To use the built-in browser tools instead:
/browser use off
Or set the backend explicitly:
browser:
backend: "off"
Restart the session after changing the configuration, then check /browser status again.
Use separate sessions for concurrent browser work
Current Hermes builds support named browser sessions:
browser_exec session=research
browser_exec session=admin
Each name gets separate Browser Use daemon state and, for a cloud provider, a separate cloud browser. Separation prevents two agents from clicking in the same tab. It does not make sensitive work safe by itself; each session still inherits the permissions and credentials of its browser source.
Compare it with the built-in tools
Run the same bounded task twice, once with Browser Use enabled and once with it off. Record:
- whether the result is correct;
- how many retries were needed;
- whether the source URL and relevant evidence were returned;
- whether a recording or audit log exists;
- the model and provider cost shown by your setup.
Use the mode that is more reliable for your actual sites. Vendor efficiency claims are useful hypotheses, not proof for your workload.
Troubleshooting
| Problem | Check |
|---|---|
| Hermes shows only built-in browser tools | Confirm the session has terminal access and browser.backend is unset or browser-use. If the engine is missing, the docs point to hermes update. |
| A catalog skill is installed and the mode is still off | Agent Browser and the browser-use skill do not select this backend. Check /browser status, terminal access, and browser.backend. |
| The wrong cloud provider opens | Select the provider in hermes tools. A saved API key alone does not select it. |
| A local browser will not connect | For your own Chrome, Brave, Chromium, or Edge, use /browser connect and a dedicated user-data directory. The default local source is packaged Chromium, not that browser. |
| Two tasks interfere with each other | Give each task a different session= name. |
| A private URL is blocked | Do not weaken the boundary by default. Decide whether that domain and browser profile are safe first. |
| The task asks for approval-sensitive action | Stop before submission and hand control to the user. |
FAQ
Why does Camofox ignore Browser Use mode?
Camofox has no CDP endpoint for the driver. The docs say those setups keep the built-in browser tools. Status output that shows the built-in tools is expected there.
I saved an API key. Why did the provider stay the same?
The key is a credential. The selected provider is the menu choice in hermes tools. After you change it, check /browser status in a new session.
The answer was confident and had no URL. Did the setup pass?
No. The verify task requires a URL you can open and a list that matches that page.
Do named sessions make the browser safe?
No. They keep concurrent tasks from sharing one tab. Cookies and approval rules are unchanged.
Can I put a password in the prompt if the profile is empty?
No. Keep passwords and recovery codes out of prompts, notes, and screenshots. Sign-in stays a human step. See L07: Security essentials before an always-on browser.
Related skills and next steps
Catalog browser skills are optional. The mode above does not depend on them.
| Skill | Use it when |
|---|---|
| Agent Browser | You want the vercel-labs CLI skill reviewed on one public page. Lesson: tools L05. Command: npx skills add vercel-labs/agent-browser --skill agent-browser |
| browser-use | You want the separate CDP skill, not the Hermes mode switch. Command: npx skills add browser-use/browser-use --skill browser-use |
| Browser Harness | You are reading the logged-in harness project. The catalog has no install command. The mode already uses that engine |
| Defuddle | You already have a URL and want clean HTML or Markdown. Command: npm install -g defuddle |
| Next | Why |
|---|---|
| First-week checklist | Day 0 through day 7 for one public page |
| Five-skill starter stack | What to install around Hermes before more browser tools |
| L04: Skills and skill bundles | Save a procedure after it works |
| L01: Hermes Agent explained | If the harness itself is still unclear |
| Skills directory | Every card linked above |
| 17-item toolkit | The longer map, including what to postpone |
Official sources
- Hermes Browser Automation, including provider setup. Checked October 22, 2026. The old
/docs/user-guide/features/browser-setuppath returned 404 that day. - Browser Use CLI