hermes-plugin-chrome-profiles

What hermes-plugin-chrome-profiles does

The plugin adds one tool, browser_profile, and one slash command, /browser-profile. Setting a profile sets BROWSER_CDP_URL, the same public override that /browser connect uses, which has top precedence in Hermes' browser backend selection. A switch therefore redirects every browser surface at once, including browser_exec, the built-in browser_navigate, browser_click, browser_snapshot and browser_vision tools, and browser_vault_fill, and it flushes live browser sessions so the next call dials the new endpoint.

Profiles are defined in the Hermes profile's config.yaml under plugins.entries.chrome-profiles.settings.profiles. Each needs a port, and may set host to make it a remote browser that is only checked for reachability, plus browser (chrome, chromium, brave, brave-origin or edge), binary, data_dir, profile_directory and headless. Edits apply on the next call without a restart. The plugin refuses to point data_dir at a browser's own default profile, since Chromium 136 and later reject remote debugging there, and it detects when another process already holds a data directory lock and fails with the PID. It is meant for dedicated work, personal or scraper identities.

Key features

• browser_profile tool and /browser-profile slash command
• Redirects every Hermes browser tool at once through BROWSER_CDP_URL
• Local profiles launched on demand and remote browsers by host and port
• Supports Chrome, Chromium, Brave, Brave Origin and Edge
• Config edits picked up without a restart
• Clear failure naming the PID when a data directory is locked

When to use it

• Letting the agent browse as a separate logged-in work identity
• Keeping a headless scraper profile apart from personal browsing
• Pointing the agent at a browser running on another machine

Who it is for: Hermes Agent users who want the agent's browser tools to use specific logged-in browser profiles.

How it fits with Hermes Agent

Built for Hermes Agent: it is a plugin that sets the same browser override as /browser connect and is configured in the Hermes profile's config.yaml.

Requirements: A Chromium-family browser: Chrome, Chromium, Brave, Brave Origin or Edge

Note: Firefox and Camofox are not supported because they have no CDP surface, and pointing data_dir at a browser's default profile is refused.

FAQ