> ## 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.

# OpenClaw setup

> Run OpenClaw's browser on Browserbase instead of OpenClaw's built-in local Chromium.

This guide recommends two Browserbase setup paths for OpenClaw, in this order:

1. Use OpenClaw's built-in browser plugin with a Browserbase profile.
2. Use the [Browse CLI](/integrations/skills/browserbase-cli) if you specifically want `browse` workflows.

## Recommended: built-in browser plugin

This is the preferred path because it keeps you inside OpenClaw's first-class browser workflow while moving execution onto Browserbase infrastructure.

<Steps>
  <Step title="Get your Browserbase API key">
    Create a Browserbase account, then copy your API key from the [Overview dashboard](https://www.browserbase.com/overview).
  </Step>

  <Step title="Configure a Browserbase browser profile">
    Add a Browserbase-backed profile in `~/.openclaw/openclaw.json`:

    ```json theme={null}
    {
      "browser": {
        "enabled": true,
        "defaultProfile": "browserbase",
        "remoteCdpTimeoutMs": 3000,
        "remoteCdpHandshakeTimeoutMs": 5000,
        "profiles": {
          "browserbase": {
            "cdpUrl": "wss://connect.browserbase.com?apiKey=<BROWSERBASE_API_KEY>",
            "color": "#F97316"
          }
        }
      }
    }
    ```
  </Step>

  <Step title="Restart OpenClaw or the Gateway">
    Restart OpenClaw so the browser service picks up the new Browserbase profile.
  </Step>

  <Step title="Verify the Browserbase profile">
    Test the profile with OpenClaw's native browser commands:

    ```bash theme={null}
    openclaw browser --browser-profile browserbase status
    openclaw browser --browser-profile browserbase open https://example.com
    openclaw browser --browser-profile browserbase snapshot
    ```
  </Step>
</Steps>

<Info>
  Browserbase creates a browser session automatically when OpenClaw connects over WebSocket, so there is no separate manual session-creation step in this flow.
</Info>

## Alternative: Browse CLI

If your workflow is centered on `browse` commands instead of OpenClaw's native browser commands, use the Browse CLI.

<Steps>
  <Step title="Install the Browse CLI">
    ```bash theme={null}
    npm i -g browse
    ```
  </Step>

  <Step title="Authenticate with your Browserbase API key">
    ```bash theme={null}
    export BROWSERBASE_API_KEY="your_api_key"
    ```
  </Step>

  <Step title="Use `browse` commands for Browserbase workflows">
    Example commands:

    ```bash theme={null}
    browse projects list
    browse sessions get <session_id>
    browse fetch https://example.com
    browse search "browser automation" --num-results 5
    ```
  </Step>
</Steps>

For the full CLI workflow reference, see the [Browse CLI guide](/integrations/skills/browserbase-cli).