Hermes browser automation just got a seriously useful upgrade. It can now run multiple browser workflows at once without taking over the browser you’re using. Hermes can now do browser work in the background without taking over the browser you are using. And the full setup is actually pretty powerful. For normal browser work, Hermes can launch its own isolated Chromium. No personal profile. No existing logins. No need to attach to your Chrome. So Hermes can be researching sites, scraping pages, testing a web app, filling forms, or running repetitive browser tasks while you keep using your computer normally. But when a job actually needs to be logged in as you, Hermes also has Real Profile mode. That lets it run against a managed copy of your browser login state, including the cookies and sessions it needs for sites you already use. So the mental model becomes: Clean browser → research, scraping, testing, anonymous workflows. Real Profile browser → X, Gmail, dashboards, SaaS tools, or anything else where your logged-in session matters. And it gets even better with multiple browser sessions. `browser_exec` can run named sessions, and each session can get its own separate Chromium instance. So one Hermes agent could be researching in one browser while another is testing something in a completely separate browser at the same time. Your browser. Hermes browser #1#. Hermes browser #2#. Hermes browser #3#. All doing different things without fighting over the same session. The newest piece is that local Browser Use now defaults to Hermes' own packaged Chromium instead of trying to attach itself to your installed Chrome. That removes a lot of the old friction around Chrome being open, remote debugging, browser popups, or Hermes interfering with the browser you are actively using. This is much closer to how browser automation should feel: You keep working. Hermes gets its own browser workspace and gets to work too.