Hermes Agent Browser Use means two things inside Hermes: Browser Use mode, which is the default way your agent drives a browser, and Browser Use cloud mode, which swaps your local browser for managed Chromium in the cloud. You get the first one out of the box. The second one needs an API key from browser-use.com. This page covers both, how to set each up, and when to pick one over the other.
📺 Watch: New Hermes Browser Use Agents are INSANE!
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
If you want the bigger picture of every browser option Hermes supports, read my Hermes Agent browser guide first. This page goes deep on Browser Use only.
And if you want to learn this stuff with people who are building agents every day, come join the AI Profit Boardroom. That's where I share my Hermes setups, workflows and walkthroughs.
Two different things share the Browser Use name
This trips people up, so let's clear it up straight away.
- Browser Use mode is a driver. It decides how the agent controls a browser. It uses the Browser Use CLI 3.0, and the agent writes and runs Python inside the browser to click, type, drag, scrape and interact with pages.
- Browser Use cloud mode is a browser source. It decides where the browser actually runs. Instead of a Chromium on your machine, Hermes uses Browser Use's managed cloud browsers.
The two stack together. Browser Use mode can drive Hermes' own headless Chromium, a Nous subscription cloud browser, Browserbase, Firecrawl, or Browser Use cloud browsers. Whatever browser source you've picked in hermes tools under Browser Automation, the driver works on top of it.
The one exception, per the docs, is Camofox. It has no CDP endpoint for the harness to attach to, so Camofox setups keep the built-in browser tools automatically.
How Hermes Agent Browser Use mode works by default
Here's the bit most people miss: you don't have to turn Browser Use mode on. It's the default. When the browser.backend setting is unset, the agent gets one tool called browser_exec instead of the usual set of separate browser tools.
The engine under the hood is browser-harness. The Browser Use CLI is a thin wrapper around it. It's a regular Python dependency of Hermes, so every install ships it, including the Desktop app. No separate download.
If it ever goes missing from your Hermes environment, Hermes falls back to the built-in browser tools, and running hermes update restores it.
It uses the packaged Chromium, not your Chrome
With no cloud provider and no /browser connect endpoint set up, Hermes launches the same packaged Chromium the built-in tools use and points the Browser Use CLI at it. Your installed Chrome is never touched.
That means:
- No remote-debugging toggle to enable.
- No "Allow remote debugging?" popup.
- It works on headless servers that have no Chrome installed at all.
The browser follows the built-in stack's lifecycle. It closes after the inactivity timeout, when Hermes exits, and during the orphan sweep. If you want the agent to use a browser you're already signed into, use /browser connect or the real-profile toggle.
Running several browser jobs at once
browser_exec takes a session name. Each name gets its own harness daemon and its own browser, on every backend. Locally that's a separate packaged Chromium. In the cloud it's a separate cloud browser.
So parallel subagents or two chats running at the same time don't trip over one shared connection. Leave the session name out and you use the shared default, which is fine for one browsing job at a time.
How to turn it off
If you'd rather have the classic built-in browser tools, type /browser use off. Or set browser.backend to "off" in your config.yaml. Setting it to "browser-use" still works if you want to force the mode on explicitly.
Browser Use cloud mode: managed Chromium with anti-bot features
Cloud mode is where Browser Use gets interesting for real-world sites. According to the Hermes docs, Browser Use Cloud gives you:
- Managed Chromium so nothing runs on your own machine.
- Stealth, enabled by default.
- Residential proxies, enabled by default.
- CAPTCHA solving included.
- Persistent profiles that reuse cookies, localStorage and saved passwords across sessions.
That last one matters. If your agent logs into a dashboard once, a persistent cloud profile means it doesn't start from zero on the next run.
How to set up cloud mode
- Get an API key from browser-use.com.
- Add BROWSER_USE_API_KEY with your key to the file at ~/.hermes/.env.
- Run hermes tools, go to Browser Automation, and pick Browser Use as your cloud provider.
Step 3 is important. The docs are clear that the .env key only supplies credentials. The active cloud browser comes from the browser.cloud_provider selection that hermes tools writes. Once you've made a selection, adding or removing a key doesn't switch providers. And if you pick a provider but the key is missing, Hermes errors and tells you to run hermes tools, rather than quietly routing somewhere else.
Brand-new setups that have never been configured still autodetect from whatever credentials are present.
The Nous Portal shortcut
If you pay for a Nous Portal subscription, the Tool Gateway can route cloud browser automation through Browser Use without you creating a separate Browser Use account. New installs can run hermes setup --portal to log in and switch on every gateway tool. Existing installs can pick Nous Subscription as the browser provider in hermes tools.
📺 Watch: Hermes Agent + Codex Browser Use Updates!
Cloud vs local: which one should you use?
| Situation | Local (packaged Chromium) | Browser Use cloud |
|---|---|---|
| Extra account or key needed | No | Yes, BROWSER_USE_API_KEY |
| Stealth and residential proxies | Not listed in the docs | On by default |
| CAPTCHA solving | Not listed in the docs | Included |
| Saved logins across sessions | Use /browser connect or real-profile toggle | Persistent cloud profiles |
| Runs on your machine | Yes | No, managed Chromium |
| localhost and LAN pages | Yes | Routed to a local sidecar by default |
Go local when you're testing, scraping friendly sites, or working on your own dev server. Go cloud when sites keep blocking your agent, throw CAPTCHAs at it, or you need logins to stick between runs without touching your own browser profile.
Not sure which way to go for your business? Book a free AI strategy session and we'll map it out.
Hybrid routing keeps your local pages private
Even with a cloud provider set, Hermes auto-spawns a local Chromium sidecar for URLs that point at private addresses, like localhost, 127.0.0.1, 192.168 ranges, or names ending in .local. Public URLs keep going to the cloud browser in the same conversation.
The docs say the cloud provider never sees the private URL. It's on by default. You can turn it off with browser.auto_local_for_private_urls set to false, but then private URLs get blocked unless you also allow them.
📺 Watch: New FREE Hermes Computer Use Agents!
Lightpanda in Browser Use mode
Lightpanda is an open-source headless browser built from scratch in Zig. The Hermes docs describe it as starting instantly, running 9x faster and using 16x less memory than Chrome. That's handy if your agent lives on a small VM.
It's a local engine, not a cloud provider. Install the binary, put it on your PATH, then pick Lightpanda in hermes tools under Browser Automation. You can also set browser.engine to lightpanda, or AGENT_BROWSER_ENGINE to lightpanda.
In Browser Use mode, Hermes launches lightpanda serve itself, one process per browser_exec session name, and points the Browser Use CLI at it. No Chromium, Playwright or Node.js needed. All those processes share one on-disk HTTP cache, so repeat visits skip re-downloading assets.
Two limits to know:
- Lightpanda has no graphical renderer, so screenshots aren't available. The agent is told to work text-first.
- It holds one page per session, so the agent opens one tab and navigates from there.
Also, the engine setting has the lowest priority. A cloud provider, Camofox, a CDP override or the real-profile toggle will all take precedence. /browser status and hermes doctor tell you when Lightpanda is configured but shadowed by something else.
For a full comparison of engines and providers, see my rundown of the best browser for Hermes.
Limits and safety
Browser Use mode runs model-written Python on your machine. That's powerful, and it's why the docs put a guard on it: browser_exec is only offered to sessions that also have terminal access. Platforms set up without the terminal toolset, like a locked-down messaging bot, keep the default browser tools instead.
A few more things worth knowing:
- Redirects from a public URL onto a private address are still blocked, so a redirect trick can't reach your LAN through the cloud path.
- The real-profile toggle copies your active browser profile into a separate snapshot. When you turn it off, Hermes deletes that snapshot on the next browser use.
- Cloud browsers need their own key. Other browser sources keep their existing credentials unchanged.
My take: start local, see what breaks, then move only the stubborn jobs to the cloud. Don't pay for anti-bot features on sites that never fight back.
If you want to see a very different take on agent browsing, check out my notes on jev-ultrafast on GitHub, the Browser Use repo that pairs their browser agent with TypeSafe's Jev decisions model.
For the full system I use to run agents day to day, read my Agent OS guide. And if you want to see how different models hold up on real tasks, look at Goldie Bench.
Want the step-by-step builds, templates and live help? Join the AI Profit Boardroom for $69/mo, with 4 live calls a week. Or grab a free AI strategy session if you'd rather talk it through first.
FAQ
Is Browser Use mode on by default in Hermes?
Yes. When browser.backend is unset, Hermes uses Browser Use mode and gives the agent the single browser_exec tool. It ships with every install, including the Desktop app.
Do I need a Browser Use API key?
Only for Browser Use's own cloud browsers. Local Browser Use mode drives Hermes' packaged Chromium with no extra key. For cloud mode, get a key at browser-use.com and add BROWSER_USE_API_KEY to ~/.hermes/.env, then select Browser Use in hermes tools.
What does Browser Use cloud add over local?
Per the Hermes docs: managed Chromium, stealth and residential proxies on by default, CAPTCHA solving, and persistent profiles that keep cookies, localStorage and saved passwords across sessions.
Can I use Lightpanda with Browser Use mode?
Yes. Pick Lightpanda in hermes tools and Hermes spawns lightpanda serve for each session, with no Chromium or Node.js needed. Screenshots aren't available because Lightpanda has no graphical renderer.
