agentos.guide › blog

The Best Browser For Hermes, And Where Each One Fits Inside An Agent OS

By Julian Goldie · 12 October 2026 · agentos.guide

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

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

After those come Browser Use Cloud, Browserbase, Camofox, Lightpanda and Firecrawl.

Here is the ranked list first, then a quick-start and the map of where each browser sits in an Agent OS.

The best browser for Hermes, ranked for an Agent OS

Here is the full ranking, with the job each browser does once Hermes sits inside an Agent OS.

This ranking is my own opinion, and it comes from the official docs, the setup menu on my own install and my daily use of Hermes.

I have not run a timed test across all eight, so where I mention speed I am quoting the docs.

I put the local Chromium first because an operating system needs a default that works for every agent, on every profile, with no key.

I put your own Chrome second because sooner or later an agent has to work inside a tool you are signed into.

What a browser means in Hermes Agent

Hermes Agent is the free, open-source AI agent from Nous Research.

Its browser toolset lets the agent open pages, click, type, fill in forms and pull information out.

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

Pages reach the model as text snapshots called accessibility trees, so the agent reads a list of labelled buttons and fields.

The default driver on top of the browser is Browser Use mode, which gives the agent one tool called browser_exec when the session also has terminal access.

I explain the toolset in my Hermes Agent browser explainer, and the driver in my Hermes Agent browser use guide.

Quick-start: get the best browser for Hermes running

This is the route I would give anyone adding a browser to their Agent OS today.

The browser toolset was already enabled when I ran the list command on my install, which is Hermes v0.21.4.

The installers and the update command set up the driver, called agent-browser, and a pinned Chromium by default.

If you skipped the browser at install time, the command hermes pm install agent-browser adds it back.

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

🔥 Want the exact Hermes browsers in the Agent OS setup I run inside my Agent OS?

Inside the AI Profit Boardroom you get the installable Agent OS, step-by-step video tutorials, four coaching calls a week and 3,400+ members building real automations.

→ Get access here

The eight browsers, one by one

1. Hermes's own local Chromium

The setup menu calls this row Local Browser, and on my install it carries the badge recommended and free.

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

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

It is best for research and public pages, and it costs nothing.

2. Your own Chrome with real profile browsing

You switch this on with the setting browser.use_real_profile in the Hermes config file.

Hermes copies your active profile into a managed snapshot and launches your real Chrome on that copy.

The docs say your live profile is never opened directly, and the copy runs headless by default.

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

It is best for dashboards and admin panels that have no API.

3. Brave, Edge or Chromium

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

Hermes copies whichever one is your operating system default.

It is best for people who do not use Chrome day to day.

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 profiles can persist cookies and saved passwords.

You add a Browser Use API key, or you use the managed version that comes with a paid Nous Portal subscription through the Tool Gateway.

It is best for an agent that runs on a server.

5. Browserbase

Browserbase needs an API key and a project ID.

The docs list basic stealth as always on and a maximum session timeout of six hours.

Hermes drops the paid extras automatically when your plan does not include them.

It is best for teams that already use Browserbase.

6. Camofox

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

You run it in Docker and point Hermes at its address.

Logins do not persist unless you turn on the managed persistence setting.

It is best for technical users who want anti-detection without a cloud bill.

7. Lightpanda

Lightpanda is a headless browser written from scratch in Zig.

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

It cannot take screenshots, so it works text-first.

It is best for small servers and bulk reading.

8. Firecrawl cloud browser

Firecrawl offers cloud browsers alongside its scraping service.

The docs give a default session length of 300 seconds.

It is best for people who already hold a Firecrawl key.

Local Browser, real profile or browser connect

These three get mixed up, so here is the difference.

The docs explain that since Chrome 136 the debugging port is ignored on your default profile.

That means the connect command needs Chrome launched with a separate user data folder, and that folder starts signed out.

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

How the browser fits inside an Agent OS

An Agent OS is one dashboard where your agents, memory and tools live together.

In mine, Hermes is the employee behind the doors, and the browser is one of the tools that employee picks up.

Different rooms need different browsers.

I already keep separate Hermes profiles for different models, and each profile has its own config, so one research profile can stay on the clean browser while a single trusted profile holds the real one.

The tour of those rooms is in the Hermes Command Desk guide.

My older guide on Hermes browser agents and the Agent OS covers the conductor idea of running many browser agents from one screen.

🔥 Want the exact Hermes browsers in the Agent OS setup I run inside my Agent OS?

Inside the AI Profit Boardroom you get the installable Agent OS, step-by-step video tutorials, four coaching calls a week and 3,400+ members building real automations.

→ Get access here

A simple workflow that uses the browser

Here is a pattern that fits the system I already run.

A scheduled job wakes the agent early in the morning.

The agent opens three competitor pages in the local Chromium and reads what changed.

It writes a short summary into the shared notes folder.

It sends the headline to my phone.

Nothing in that chain needs a login, so the clean browser is the right one.

If I wanted the same job to read a signed-in dashboard, the docs list three things to do first.

I would turn real profile browsing on, give the cron job the browser toolset and save the login in the vault ahead of time.

Browser versus computer use

People ask whether computer use replaces the browser.

The docs say browser work, including pages in a signed-in profile, goes through the browser toolset and not the computer use toolset.

Computer use is for desktop apps, and it drives them in the background on macOS, Windows and Linux.

In my Hermes computer use guide, a Notes app test finished in under eight seconds, and a bigger Obsidian reorganising job struggled.

I also said in that guide that the feature was experimental and that a secondary machine is a sensible place to try it.

I give the browser the web and computer use the apps.

Safety for logged-in sessions and approvals

A browser that holds your logins is the most sensitive tool in the whole system.

The docs call real profile browsing a consent-gated convenience and not an isolation boundary.

Turning the real profile setting off makes Hermes delete the copied profile on the next browser use.

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

The docs also warn that the unrestricted approval mode gives no protection against prompt injection.

Limits to know before you rely on it

The docs say the browser toolset cannot download files.

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

Cloud sessions use provider credits, and they are cleaned up after the conversation ends or goes idle.

Firefox as your default browser fails closed for real profile browsing, and Safari is not in the supported list.

The docs suggest web search and extract for simple lookups, because they are faster and cheaper than a browser.

What to do next

Get the free local browser working first.

Then pick one real job from my best Hermes Agent tools list and hand it over.

FAQ

What is the best browser for Hermes?

My top pick is the free local Chromium that Hermes Agent installs for itself, listed as Local Browser in the setup menu. It needs no API key and holds none of your logins. Your own Chrome with real profile browsing is second, and Brave, Edge or Chromium is third.

Can Hermes use my own Chrome with my logins?

Yes. Set browser.use_real_profile to true in the Hermes config file. Hermes copies your active profile into a managed snapshot and drives that copy, so your live profile is never opened directly. The setting is off by default.

Does Hermes work with Firefox or Safari?

Not as your real profile browser. The docs say a non-Chromium default such as Firefox fails closed, and Safari is not in the supported list. Camofox is the Firefox-based option, and it runs as a separate server.

Do I need a cloud browser for Hermes?

Most people do not. The local Chromium is free and covers research and logged-in work on your own computer. A hosted browser helps when the agent runs on a server or a site blocks ordinary automation.

Is the browser the same as Hermes computer use?

No. The docs send web work, including signed-in pages, to the browser toolset. Computer use is a separate toolset that drives desktop apps in the background on macOS, Windows and Linux.

Final word on the best browser for Hermes

Start with the local Chromium that is already installed, and add your own Chrome only when a job needs your logins.

Keep approvals on, use the vault for passwords, and you will have the best browser for Hermes.

Related guides on agentos.guide

→ Free Hermes Computer Use Agents

→ Hermes Browser Agents + Agent OS

→ The Hermes Command Desk

→ Build Your Own AI Agent OS

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide