The best browser for Hermes is the default one: Browser Use mode driving Hermes' own packaged Chromium. Per the Hermes docs, it's the default browser mode, it ships with every install (Desktop app included), it needs no API key, and it never touches your own Chrome. You get a working browser agent the moment you install.
📺 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
That said, the right pick changes with the job. If you need stealth and CAPTCHA solving, a cloud browser wins. If you want to watch the agent click around with your own logins, your local Chrome wins. Below is every browser option the Hermes docs list, ranked, with what each one is actually good for.
I run Hermes every day inside my own Agentic Operating System, with a separate profile per model. If you want the full setup handed to you, the AI Profit Boardroom ($69/mo) has Hermes courses, the Agent OS zip, daily updates and 4 coaching calls a week.
Quick ranking: the best browser for Hermes
| # | Option | Type | Best for | Needs |
|---|---|---|---|---|
| 1 | Browser Use mode (packaged Chromium) | Local, default | Most people, zero setup | Nothing extra |
| 2 | Browser Use Cloud | Cloud | Stealth, proxies, CAPTCHA solving | BROWSER_USE_API_KEY |
| 3 | Your Chrome, Brave, Chromium or Edge via CDP | Local | Watching live, free browsing | /browser connect in the CLI |
| 4 | Browserbase | Cloud | Anti-bot tooling, full dialog handling | API key and project ID |
| 5 | Nous Subscription browser | Cloud | Portal subscribers, no separate keys | Paid Nous Portal plan |
| 6 | Lightpanda | Local engine | Small VMs, low memory | Lightpanda binary on PATH |
| 7 | Camofox | Local, self-hosted | Anti-detection without the cloud | Camofox server, CAMOFOX_URL |
| 8 | Firecrawl | Cloud | Cloud browsing with built-in scraping | FIRECRAWL_API_KEY |
| 9 | Local browser mode (agent-browser) | Local | Built-in tools, no cloud credentials | agent-browser and Chromium |
1. Browser Use mode with packaged Chromium
This is #1 because the Hermes docs make it the default. When browser.backend is unset, the agent gets a single browser_exec tool and writes Python in the browser to click, type, drag and scrape. The engine is browser-harness, which is a regular Python dependency of Hermes, so there's no separate download.
With no cloud provider or /browser connect endpoint set, Hermes launches its own packaged Chromium. Your installed Chrome is never touched, so there's no remote-debugging toggle and no "Allow remote debugging?" popup. It even works on headless servers with no Chrome at all.
It also handles parallel work. browser_exec takes a session name, and each name gets its own daemon and its own browser, so subagents don't trip over each other. One catch from the docs: because it runs model-written Python, browser_exec is only offered to sessions that also have terminal access.
2. Browser Use Cloud
When sites fight back, this is the upgrade. Per the docs, Browser Use Cloud runs managed Chromium with stealth and residential proxies on by default, includes CAPTCHA solving, and supports persistent profiles for cookies, localStorage and saved passwords.
Setup is one line in ~/.hermes/.env: BROWSER_USE_API_KEY, which you get from browser-use.com. Then pick it in hermes tools under Browser Automation. Browser Use mode drives it the same way it drives local Chromium, so nothing about how the agent works changes.
📺 Watch: NEW Hermes Desktop Browser Update Is INSANE!
3. Your own Chrome, Brave, Chromium or Edge via CDP
Run /browser connect in the Hermes CLI and the browser tools attach to your own running browser over the Chrome DevTools Protocol. The docs say this is useful when you want to see what the agent is doing in real time, use pages that need your cookies, or avoid cloud costs. The docs' own limits section says to use /browser connect for free local browsing.
It's also the only route that unlocks browser_cdp, the raw DevTools escape hatch, and the full browser_dialog workflow for alerts and prompts. Two gotchas from the docs: /browser connect only works in the interactive CLI, not in Telegram or Discord, and on Chrome 136+ you need a dedicated user-data-dir, like $HOME/.hermes/chrome-debug, or the debug port never opens.
If you want your existing logins without any of that, the docs point to browser.use_real_profile instead. It snapshots your active profile and drives the copy. It's off by default and it's a consent-gated convenience, not an isolation boundary.
4. Browserbase
Browserbase is the other big cloud option. You add BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID to ~/.hermes/.env. Per the docs, basic stealth is always on, residential proxies are on by default, and advanced stealth needs a Scale Plan. If paid features aren't on your plan, Hermes falls back automatically so browsing still works on free plans.
Browserbase also gets the full dialog workflow through an injected bridge, and session recording works in both local and Browserbase modes. Each task gets its own isolated session, cleaned up after two minutes of inactivity by default.
📺 Watch: Hermes AI Browser Agent: Build ANYTHING!
5. Nous Subscription browser
If you already pay for Nous Portal, the docs say you can use browser automation through the Tool Gateway without separate API keys. New installs can run hermes setup --portal to log in and turn on every gateway tool at once. Existing installs pick Nous Subscription as the browser provider in hermes model or hermes tools.
6. Lightpanda
Lightpanda is a headless browser built from scratch in Zig. The docs describe it as starting instantly, running 9x faster and using 16x less memory than Chrome, which matters for agents living on small VMs. In Browser Use mode, Hermes spawns it itself, with no Chromium or Node needed.
The trade-off: it has no graphical renderer, so screenshots aren't available in Browser Use mode. With the built-in tools, Hermes falls back to Chrome automatically for anything Lightpanda doesn't support yet. Note that the engine setting is the lowest priority, so a cloud provider or /browser connect overrides it.
7. Camofox
Camofox is a self-hosted Node.js server wrapping Camoufox, a Firefox fork with fingerprint spoofing. It gives you local anti-detection browsing with no cloud dependency. You run the server, often in Docker, then set CAMOFOX_URL in ~/.hermes/.env and pick Camofox in hermes tools.
It ranks lower because it has no CDP endpoint. Browser Use mode can't attach to it, so Camofox keeps the built-in tools, and browser_dialog detection isn't available. Persistent logins need browser.camofox.managed_persistence set to true at that exact nested path.
8. Firecrawl
Firecrawl is a cloud browser with built-in scraping. Add FIRECRAWL_API_KEY to ~/.hermes/.env, then run hermes setup tools and choose Browser Automation, then Firecrawl. You can also point FIRECRAWL_API_URL at a self-hosted instance. Session TTL defaults to 300 seconds.
9. Local browser mode (agent-browser)
This is the built-in browser tools path: browser_navigate, browser_snapshot, browser_click, browser_type and the rest, driven through the agent-browser CLI and a local Chromium. You get it with /browser use off, or by setting browser.backend to off. Pages come back as accessibility trees with ref IDs like @e1, which is easy for a model to read.
It's the fallback the whole system leans on, but most people are better off with the default Browser Use mode on top of the same Chromium.
How to pick fast
- Just starting? Leave the default. It works out of the box.
- Getting blocked by sites? Move to Browser Use Cloud or Browserbase.
- Want to watch and stay free? Use /browser connect with your own Chrome.
- Running on a tiny VM? Try Lightpanda.
For the full setup walkthrough, read my Hermes Agent browser guide. If you need the agent to control desktop apps rather than web pages, see Hermes computer use. And for simple lookups, the docs say web_search and web_extract are faster and cheaper than a browser, so check Hermes Agent web search first.
The model you pair with the browser matters too. I track model results on Goldie Bench, and the Agent OS guide shows how I run Hermes alongside everything else. Want help mapping this to your business? Book a free AI strategy session.
FAQ
What is the best browser for Hermes?
The default Browser Use mode with Hermes' packaged Chromium. Per the Hermes docs it's the default, ships with every install and needs no API key or setup.
Can Hermes use my own Chrome?
Yes. Run /browser connect in the Hermes CLI to attach to Chrome, Brave, Chromium or Edge over CDP. On Chrome 136+ start it with a dedicated user-data-dir so the debug port opens.
Which Hermes browser handles CAPTCHAs?
Per the docs, Browser Use Cloud includes CAPTCHA solving, and Browserbase's basic stealth includes it too. Both are paid cloud services with their own keys.
Is the Hermes browser free?
The local options are. Cloud sessions use provider credits, and the docs suggest /browser connect for free local browsing.
Ready to build agents that browse, research and work for you? Join the AI Profit Boardroom for the Hermes courses and Agent OS, or grab a free AI strategy session and we'll map out your setup.
