Hermes Agent includes built-in browser automation with multiple backend options, including Browserbase cloud mode. For Browserbase users, the recommended Hermes integration path is Hermes’ built-in Browserbase browser support. If you want access to additional Browserbase platform features and more granular control over browser sessions, use the Browse CLI path second.Documentation Index
Fetch the complete documentation index at: https://docs.browserbase.com/llms.txt
Use this file to discover all available pages before exploring further.
Recommended order
1. Built-in Browserbase mode
Recommended. Use Hermes’ native browser tooling with Browserbase as the cloud browser provider.
2. Browse CLI
Use this when you want additional Browserbase platform features and more granular control over sessions, contexts, logs, fetch, search, and browser configuration.
Setup paths
| Order | Path | Best for |
|---|---|---|
| 1 | Built-in Browserbase setup | Users who want Hermes’ native browser commands to run on Browserbase |
| 2 | Browse CLI | Users who want browse commands for sessions, projects, functions, fetch, and search |
Common use cases
- Run Hermes browser tasks on Browserbase instead of a local Chromium install
- Give Hermes access to Browserbase sessions with managed cloud browsers, residential proxies, and anti-bot tooling
- Keep Hermes’ native browser workflow while moving browser execution to Browserbase infrastructure
Next step
Hermes setup guide
Start with the recommended Hermes Browserbase cloud mode configuration.
Browse CLI guide
Use the Browse CLI if your workflow is centered on
browse.