Why it matters
Profile
Switch browser tools between Chrome profiles via CDP. Useful for multi-account testing or browsing with different saved sessions.
setup mediumintegration highinterface web
Provenance
Signals
Listed in the awesome-hermes-agent README
Sources: 2 / Surfaces: 1
Fast skim
What the upstream surface says
Short excerpt only, so you can decide whether to click out.
Switch the agent's browser tools between multiple Chrome or Microsoft Edge instances via CDP (Chrome DevTools Protocol). Each profile maps to a browser instance with its own user data directory, cookies, and authenticated sessions.
Supports both Google Chrome (--user-data-dir) and Microsoft Edge (--profile-directory).
The plugin registers a single tool: browser_profile(name).
Chrome/Edge Profiles PluginHow it worksConfigurationOptional: global Chrome binary path (overrides PATH auto-detection)chrome_binary: /opt/google/chrome/google-chromeOptional: per-profile Chrome binary overridechrome_binary: /usr/bin/google-chrome-betaMicrosoft Edge profile (no datadir, uses profiledirectory)
- Looks up the named profile in config.yaml
- Remote profiles — checks if host:port is reachable. Fails immediately if not (no launch attempt).
- Flushes any stale browser sessions from previous connections.
- Profile-level chrome_binary field
- Top-level chrome_binary field
- Auto-detect from PATH: google-chrome, google-chrome-stable, google-chrome-beta, chromium-browser, chromium
- Profile-level edge_binary field
- Top-level edge_binary field