Hermes Agent

Feature

Hermes Agent Browser Automation: Browser Use, Cloud Browsers, and Local Chrome

Quick answer

Hermes uses browser_exec through its bundled Python browser harness when browser and terminal tools are enabled. Local Chromium needs no cloud key and starts with a clean profile. Choose cloud, live CDP or real-profile browsing deliberately. Lightpanda is text-first with no screenshots; Camofox now lives in a plugin.

Key Points

  • ✓browser_exec is supplied by the bundled browser harness and requires terminal access; terminal-restricted sessions do not get the core browser tool.
  • ✓Local Chromium launches headless with a clean profile and needs no cloud key. Install a missing package with hermes pm install chromium.
  • ✓Cloud sources include Nous subscription access, Browserbase, Browser Use cloud and Firecrawl; saved provider selection controls the source.
  • ✓Named sessions isolate workflows. Reuse the same name per workflow; browser state persists, Python variables do not.
  • ✓Real-profile snapshots and live CLI CDP are explicit account-access choices; verify intended identity before private work.
  • ✓Lightpanda has no screenshots and one page per session. Camofox is a separate plugin, not the legacy core fallback.
  • ✓A page opening, field changing, submission and durable saved output are separate success states.

How It Works

  1. 1Enable Browser Automation through hermes tools on the intended surface, with terminal access deliberately permitted.
  2. 2Select a source, repair missing local Chromium if needed, and follow the browser setup walkthrough linked below.
  3. 3Read a permitted public page with a known heading and record final URL/ready state before adding account access.
  4. 4Use a real-profile snapshot or CLI /browser connect only when needed; stop authenticated actions on a wrong or unavailable identity.
  5. 5Test a harmless form field without submitting. Inspect final record/output separately after any authorized write.
  6. 6Follow the browser troubleshooting guide linked below for tool, launch, account, transport and page-script failures.

Real-World Use Cases

Rendered page QA

Use Chromium for desktop/phone screenshots, headings, layout, console and final-state inspection. Lightpanda cannot supply graphical screenshots.

Authorized account work

Choose an intended real-profile snapshot, approved live CDP session or supported vault login. Verify identity without recording secrets before any private action.

Public research plus private development

A local sidecar can read private URLs from the Hermes host while a configured cloud source handles public URLs. Confirm which machine owns localhost.

Bounded recurring observations

Define expected page, account and output states. Report login or access blockers rather than silently claiming a scheduled browser task succeeded.

Missing tool is not missing credit

Check both browser and terminal tools on the active surface. Current browser_exec runs Python; a deliberately restricted session does not inherit a legacy fallback.

Missing Chromium has a package repair

Run hermes pm install chromium after a skipped or failed download. Local Chromium needs no separate cloud key or everyday Chrome window.

Choose visual or text-only evidence

Lightpanda has no screenshot renderer and one page per session. Use Chromium when the job requires visual QA; check engine shadowing with /browser status and hermes doctor.

Inspect the page before its private runtime

A script that assumes an undocumented application object can fail after the site changes. Check final URL, expected DOM and readiness before diagnosing credentials.

A profile snapshot is an explicit identity choice

real_profile_unavailable means public browsing may continue signed out, not that private actions are authorized. Windows can reuse an older copy; verify the intended current account.

Browser chat is not browser control

The self-hosted dashboard can chat in a browser. Website automation separately requires the right runtime, toolsets, source, network and account permissions.

Under the Hood

The current browser harness ships as a Hermes Python dependency, including in Desktop. browser_exec runs model-written Python and therefore requires terminal access. The current official guide does not promise the old built-in browser fallback on locked-down surfaces.

Ordinary local browsing launches packaged Chromium, headless and signed out, without touching your everyday browser. Current installers and updates normally install it; hermes pm install chromium repairs a skipped or failed download. A missing browser package is not a reason to buy cloud credits.

A saved browser.cloud_provider selection wins over credential autodetection. Hybrid routing can send private URLs written into a browser call to a local Chromium sidecar on the Hermes host while public URLs stay in the cloud. A container/VPS localhost is not the operator’s laptop; do not weaken network protections to conceal that difference.

Real-profile browsing creates a credential-bearing managed snapshot, not a sandbox. Check real_profile_unavailable and intended identity before private actions. On Windows, first-copy locks and later reuse of an older snapshot differ from macOS/Linux cookie copying with skipped password/autofill files.

Lightpanda is text-first, without graphical screenshots and with one page per session; do not promise universal Chrome fallback. Camofox moved to a plugin with migration rules for recognized older setups. Choose the right engine and current plugin instructions before diagnosing a failure.

Self-hosted Web Dashboard already includes browser chat. FlyHermes changes who operates the host and updates; it does not automatically grant the agent your laptop’s cookies, private network or arbitrary site access.

Frequently asked questions

What tools does current Hermes browser automation use?

browser_exec is the main Python-driving tool, with browser_vault for supported secret-safe credential use. Standalone browser_cdp and browser_dialog are offered only while a CDP endpoint is configured; the cdp helper is available inside browser_exec.

Can Hermes browse on a headless server?

Yes, ordinary local Chromium is headless by default. The host still needs a usable Chromium package and required system libraries; a display is not a prerequisite.

Can Lightpanda produce screenshots?

No graphical screenshots are available according to current docs. It is a text-first engine with one page per session. Choose Chromium deliberately for screenshot-based QA.

Is Camofox still a core backend?

Current docs move Camofox to a plugin, installed with hermes plugins install camofox. Recognized existing configurations are migrated on update; check current plugin setup rather than legacy core keys.

Can a hosted browser use my laptop login automatically?

Do not assume so. Account connections and private-network reach must be verified for the chosen service and workflow. Managed chat access is not proof of arbitrary authenticated browser support.

What counts as a completed browser action?

Verify the expected final state or durable record, not just a click or screenshot. Navigation, intended identity, field entry, submission and saved output require separate evidence.

Next setup steps

Related Features