Skip to main content
OpenClaw is an agent runtime with built-in tools, workspace automation, and browser control. For Browserbase users, the recommended OpenClaw integration path is the built-in browser plugin with a Browserbase-backed browser profile.
See Remote browser vs local browser for why Browserbase’s managed browser beats self-hosted Chromium.
If you want to stay inside OpenClaw’s native browser experience, start there first. If you want access to additional Browserbase platform features and more granular control over browser sessions, use the CLI path second.

1. Built-in browser plugin

Recommended. Use OpenClaw’s first-class browser integration with a Browserbase remote profile.

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.

​
Common use cases

  • Run OpenClaw browsing tasks on Browserbase instead of a local Chromium install
  • Give OpenClaw access to Browserbase sessions with residential proxies, CAPTCHA handling, and session observability
  • Keep local OpenClaw orchestration while moving browser execution to Browserbase infrastructure