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.

Paper-cutout illustration of an empty window frame like a puppet theater, with a paper cursor pulling levers connected to gears
Reading time
9 min
Last updated
October 2026

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.

Official Hermes documentation explaining when Browser Use mode is the default
August 27, 2026 capture of the Browser Use section. The October 22, 2026 page still describes browser_exec, terminal access, and the Camofox exception, and it now says the mode is the default when browser.backend is unset. The screenshot itself was not recaptured.

Choose the browser source

Browser Use is the driver. You still choose where the browser runs.

NeedStart withTrade-off
A clean local browserPackaged Chromium, the default local sourceSeparate from your signed-in Chrome. Install it from hermes tools
Watch an existing local browserChromium-family CDP via /browser connectShares that machine and can expose a signed-in session
Browse with your current loginsReal-profile toggle, off by defaultCopies cookies into a snapshot. Consent, not an isolation boundary
Run remotely or on a scheduleBrowser Use Cloud, Browserbase, Firecrawl, or Nous SubscriptionSends page content and actions to that provider
A lighter local engineLightpanda, where the page fitsSome actions fall back to Chrome. Speed claims still need your own timing
Use CamofoxBuilt-in Hermes browser toolsCamofox 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

ProblemCheck
Hermes shows only built-in browser toolsConfirm 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 offAgent Browser and the browser-use skill do not select this backend. Check /browser status, terminal access, and browser.backend.
The wrong cloud provider opensSelect the provider in hermes tools. A saved API key alone does not select it.
A local browser will not connectFor 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 otherGive each task a different session= name.
A private URL is blockedDo not weaken the boundary by default. Decide whether that domain and browser profile are safe first.
The task asks for approval-sensitive actionStop 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.

Catalog browser skills are optional. The mode above does not depend on them.

SkillUse it when
Agent BrowserYou 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-useYou want the separate CDP skill, not the Hermes mode switch. Command: npx skills add browser-use/browser-use --skill browser-use
Browser HarnessYou are reading the logged-in harness project. The catalog has no install command. The mode already uses that engine
DefuddleYou already have a URL and want clean HTML or Markdown. Command: npm install -g defuddle
NextWhy
First-week checklistDay 0 through day 7 for one public page
Five-skill starter stackWhat to install around Hermes before more browser tools
L04: Skills and skill bundlesSave a procedure after it works
L01: Hermes Agent explainedIf the harness itself is still unclear
Skills directoryEvery card linked above
17-item toolkitThe longer map, including what to postpone

Official sources