Browser

OpenClaw can maintain a dedicated Chromium profile for agents, or attach to an existing Chrome instance through a relay extension. The goal is to keep browser automation separate from your personal browser while still offering controllable tabs and page actions.

Tools Overview Exec Remote Access

Quick Start

Basic commands

openclaw browser --browser-profile openclaw status
openclaw browser --browser-profile openclaw start
openclaw browser --browser-profile openclaw open https://example.com
openclaw browser --browser-profile openclaw snapshot

Default browser config

{
  browser: {
    enabled: true,
    defaultProfile: "chrome",
    profiles: {
      openclaw: { cdpPort: 18800, color: "#FF4500" }
    }
  }
}

Profile Types

Managed

openclaw

A dedicated managed browser instance isolated from your personal profile, best for reliable automation.

Relay

chrome

Controls the system browser through a local relay and extension. Convenient for shared workflows, but with weaker isolation.

Remote

Remote CDP

Can attach directly to a remote Chromium CDP URL, but this is effectively operator-level access and should be protected carefully.

Node Proxy

Node browser proxy

When the Gateway and browser live on different machines, let the node host proxy the browser instead of exposing browser control services directly.