The Best Browser For Hermes, Ranked, And The Models That Drive It Well

The best browser for Hermes is the free local Chromium that Hermes Agent installs for itself, which the setup menu calls Local Browser.

My second pick is your own Google Chrome with real profile browsing, and my third pick is Brave, Edge or Chromium.

Hermes Agent is the free, open-source AI agent from Nous Research, and its browser toolset lets the agent open pages, click, type and fill in forms.

The browser you pair with it is called a backend, and the official docs list eight ways to supply one.

This is my own ranking from the docs, my own install and my daily use of Hermes, so the order is my opinion and not a measured result.

Below you'll get all eight, how to set up the winner, the safety rules for logged-in sessions, and then a later section on which model to put in the driving seat.

The best browser for Hermes at a glance

My top three are all free and all local, because that's where most people should start.

What a browser means in Hermes Agent

The browser toolset is one of the built-in toolsets you manage with hermes tools.

The docs say pages are represented as accessibility trees, which are text snapshots where every button and field gets a short reference.

That's why the agent doesn't need to look at pixels for most web work.

There are two drivers on top of the browser.

Browser Use mode is the default, and it gives the agent a single tool called browser_exec that runs short Python in the page.

The built-in browser tools are the alternative, with separate tools such as browser_navigate, browser_click and browser_type.

The docs say browser_exec is only offered to sessions that also have terminal access, so a locked-down messaging bot keeps the built-in tools.

I cover the toolset in my explainer on the Hermes Agent browser, and the driver in my post on Hermes Agent browser use.

How I ranked the browsers

I looked at five things.

I asked whether the browser works out of the box.

I asked how reliable it is with logins.

I asked how fast and light it is, going by the figures in the docs.

I asked what it costs.

I asked how private it is.

I haven't timed these backends against each other, so any speed figure below is quoted from the Hermes docs.

The eight browsers, one by one

1. Hermes's own local Chromium

Hermes installs a pinned Chromium and a driver called agent-browser, and hermes update keeps both current.

On my install, which is Hermes v0.21.4, the hermes tools menu lists this row as Local Browser with the badge "★ recommended · free".

The docs say local browsing uses this packaged Chromium and never touches your installed Chrome.

It runs in a clean, throwaway profile, so the agent is logged into nothing.

It's free, and hermes pm install agent-browser adds it back if you skipped it at install time.

2. Your own Chrome with real profile browsing

You switch this on with browser.use_real_profile: true in ~/.hermes/config.yaml.

Hermes copies your active profile into a managed snapshot under ./.hermes/browser-profile/ and launches your real Chrome binary on that copy.

The docs say that's what keeps operating-system-encrypted cookies readable, and your live profile is never opened directly.

The copy runs headless by default, so nothing pops up on your screen.

You should fully quit Chrome first, because the docs say a running browser locks the login databases.

It's free, and it's off by default.

3. Brave, Edge or Chromium

The docs list Chrome, Edge, Brave, Brave Origin and Chromium as supported for real profile browsing.

Hermes uses whichever one is your operating system default.

The /browser connect command also detects Brave, Chrome, Chromium and Edge.

It's the pick for anyone who doesn't live in Chrome.

4. Browser Use Cloud

Browser Use Cloud is managed Chromium on a provider's servers.

The docs say stealth and residential proxies are on by default, CAPTCHA solving is included and persistent profiles keep cookies and saved passwords.

You add BROWSER_USE_API_KEY to ~/.hermes/.env and select the provider in hermes tools.

A paid Nous Portal subscription includes the same managed browser through the Tool Gateway.

5. Browserbase

Browserbase needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID.

The docs list basic stealth as always on, residential proxies as on by default and a maximum session timeout of six hours.

Hermes turns off the paid extras automatically when your plan doesn't include them, so browsing still works.

6. Camofox

Camofox is a self-hosted server that wraps Camoufox, a Firefox fork with fingerprint spoofing.

You run it in Docker and set CAMOFOX_URL to its address.

Logins don't persist unless you set browser.camofox.managed_persistence: true.

Camofox has no Chrome DevTools endpoint, so Hermes keeps the built-in browser tools for it.

7. Lightpanda

Lightpanda is a headless browser written from scratch in Zig.

The Hermes docs say it starts instantly, runs nine times faster than Chrome and uses sixteen times less memory.

It has no graphical renderer, so it can't take screenshots, and it holds one page per session.

With the built-in tools, Hermes falls back to Chrome automatically for anything Lightpanda can't do.

8. Firecrawl cloud browser

Firecrawl offers cloud browsers alongside its scraping service.

You add FIRECRAWL_API_KEY and choose Firecrawl under Browser Automation.

The docs give a default session length of 300 seconds.

The eight compared

How to set up the best browser for Hermes

The browser toolset was already enabled when I ran the list command on my install.

On Linux, the docs say Chromium may need extra system libraries.

Real profile browsing versus /browser connect

These two both involve your own browser, and they aren't the same thing.

Real profile browsing drives a copy of your active profile, so it has your real logins and it works in the background.

The /browser connect command attaches Hermes to a running Chromium browser over the Chrome DevTools Protocol on port 9222.

The docs say it only works in the terminal chat, because it isn't dispatched from Telegram, Discord or the web UI.

Since Chrome 136, the debugging port is ignored on your default profile, so the docs tell you to launch Chrome with a dedicated --user-data-dir.

That dedicated profile starts signed out.

I use /browser connect when I want to watch the agent in a real window, and real profile browsing when the job needs my logins.

Safety for logged-in sessions and approvals

A browser that holds your logins is the most sensitive thing you can hand an agent.

The docs call real profile browsing a consent-gated convenience and not an isolation boundary, which means any page the agent visits runs with your real logins.

I leave it off until a job needs it, and I turn it off again afterwards.

The docs say Hermes deletes the copied profile on the next browser use once the setting is off.

I use the vault for passwords, which the hermes vault help text says stores logins in a locally encrypted vault and never puts passwords into the conversation.

I set browser.restrict_evaluate: true when the agent browses unknown pages with a logged-in profile.

I keep approvals on, because the docs warn that the unrestricted mode doesn't protect against prompt injection.

Hermes also asks before it closes your browser to free a locked profile, and it never does that on its own.

In my computer use video, I called this level of access experimental and said a secondary machine is a sensible place to try it.

Limits and browsers I'd skip

The docs say the browser toolset can't download files.

Long pages are cut at 15,000 characters by default, and the full snapshot is saved to a file the agent can page through.

Cloud sessions use provider credits.

Firefox as your default browser fails closed for real profile browsing, and Safari isn't in the supported list.

The computer_use toolset isn't a browser replacement, because the docs send web work to the browser toolset.

The docs suggest web_search and web_extract for simple lookups, because they're faster and cheaper.

Does the Hermes browser come with its own model?

No, it doesn't, because the browser is only the hands.

Every click and every form field is chosen by whichever model you've connected to Hermes.

A browser job is a long chain of small decisions, so a weak brain gets lost in the same Chromium where a strong brain finishes the job.

I use GoldieBench to shortlist that brain, and I want to be straight about what the board measures.

GoldieBench gives each model the same one-shot prompt to build a game, a page, a simulation or a visual, then scores the rendered result from 0 to 10.

It doesn't run a browsing test, so these numbers show how well a model holds a hard multi-step job together, not how it scores at clicking through websites.

I still use them as a guide, because a model that finishes a hard build in one shot is usually a safer pair of hands on a long browser task.

Which model to put behind your Hermes browser

Every number matched the live model page when I checked on 12 October 2026.

How I match browsers to brains

The clean local Chromium and a cheap model make a good pair for public research, because a mistake costs almost nothing.

Real profile browsing is where I move up to a stronger model, because the agent is acting as me.

Lightpanda is text-only, so the tool description tells the model to work text-first, and any tool-capable model can do that.

The browser_vision tool takes a screenshot and analyses it with vision AI, so a vision-capable setup helps on pages where the text snapshot misses something.

Page snapshots can be long, so a model with a large context window copes better with heavy pages.

For the full ranking of brains, read my post on the best LLMs for Hermes Agent, and for the wider toolset read my list of the best Hermes Agent tools.

A quick test before you trust a browser setup

I'd run the same short routine on any new pairing.

First, I'd give the agent three public pages to read and summarise.

Second, I'd ask it to fill in a harmless form on a test page.

Third, I'd watch one run in headed mode to see where it hesitates.

Fourth, I'd swap to a cheaper model and repeat the same jobs.

If the cheaper model handles them, I'd leave public browsing there and keep the stronger model for logged-in work.

Also On Our Network

• Agent Operatorsthe setup steps for every Hermes browser
• AI Income Deskpicking a Hermes browser by the business job
• AI Tool Verdictall eight Hermes browsers scored out of ten
• agentos.guidewhere the Hermes browser fits inside an Agent OS
• agentos.guideJulian's free Hermes computer use guide

Start with the free local Chromium, add your own Chrome when a job needs your logins, put a proven brain behind it, and you'll have the best browser for Hermes.