OpenClaw Browser Automation & Chrome Extension Guide

One of OpenClaw's most powerful features is its ability to control a web browser. It can fill out forms, scrape data, take screenshots, interact with web apps, and automate any task you would normally do manually in Chrome. This guide covers all three browser modes and shows you how to set them up.

How Browser Automation Works

OpenClaw can control a Chrome or Chromium browser just like a human would—clicking buttons, typing text, navigating pages, and reading content. It uses this capability for tasks like price tracking, form submission, data extraction, and interacting with web applications that do not have APIs. The browser runs headlessly (no visible window) on your server, so it works perfectly for 24/7 automation.

Three Browser Modes

OpenClaw supports three ways to connect to a browser, each suited for different use cases. Managed mode is the simplest—OpenClaw launches and controls its own browser instance. CDP mode connects to an existing browser via Chrome DevTools Protocol, useful if you want to use a specific browser profile with saved logins. Extension Relay mode uses a lightweight Chrome extension to bridge your personal browser to OpenClaw, great for tasks that require your authenticated sessions.

Managed Browser Setup (Recommended)

The managed browser mode is the easiest to set up and the most reliable. OpenClaw automatically installs and manages a Chromium instance. This is the recommended mode for most users, especially for server deployments where you want fully automated operation.

# Managed browser is enabled by default
# Just verify it works:
openclaw browser status

# Configuration options in openclaw.json:
{
  "browser": {
    "mode": "managed",
    "headless": true,
    "defaultViewport": {
      "width": 1280,
      "height": 800
    }
  }
}

# Test with a simple task via Telegram:
# "Take a screenshot of google.com"
# "What is the current price on amazon.com/dp/B0..."

Chrome Extension Relay Setup

The Chrome Extension Relay lets OpenClaw control your personal Chrome browser. This is useful when you need to interact with websites where you are already logged in—like banking portals, internal company tools, or subscription services. The extension acts as a bridge between OpenClaw and your browser, forwarding commands securely.

# 1. Install the OpenClaw Browser Relay extension
# Available on the Chrome Web Store
# Search: "OpenClaw Browser Relay"

# 2. Configure the extension
# Click the extension icon > Settings
# Enter your OpenClaw Gateway URL:
# http://127.0.0.1:18789 (or your Tailscale IP)
# Enter your pairing code

# 3. Update OpenClaw config:
{
  "browser": {
    "mode": "extension",
    "extensionId": "your-extension-id"
  }
}

# 4. Test the connection:
# Via Telegram: "Check my bank balance"
# (uses your logged-in Chrome session)

CDP (Chrome DevTools Protocol) Mode

CDP mode connects to any Chrome browser that has remote debugging enabled. This gives you the most flexibility—you can connect to Chrome on a different machine, use a specific user profile, or integrate with existing browser automation setups. It is more technical to configure but offers the most control.

# 1. Launch Chrome with remote debugging
google-chrome --remote-debugging-port=9222 \
  --user-data-dir=/tmp/chrome-profile

# 2. Configure OpenClaw to connect
{
  "browser": {
    "mode": "cdp",
    "cdpUrl": "http://127.0.0.1:9222"
  }
}

# 3. Verify connection
openclaw browser status
# Should show: Connected to Chrome via CDP

# This is useful for:
# - Using saved logins from a Chrome profile
# - Connecting to Chrome on another machine
# - Integrating with existing Selenium setups

Browser Automation Use Cases

Here are five popular ways people use OpenClaw's browser automation: Price Tracking—monitor product prices across e-commerce sites and alert you on drops. Form Automation—fill out repetitive online forms, job applications, or government paperwork. Data Scraping—extract structured data from websites that do not offer APIs. Screenshot Monitoring—take periodic screenshots of dashboards or web pages to detect changes. Web App Interaction—interact with web applications like booking systems, admin panels, or social media platforms on your behalf.

Security & Permissions

Browser automation is powerful, which means it requires careful security consideration. OpenClaw's browser runs in a sandboxed environment with restricted access to your filesystem. When using the Chrome Extension Relay, all communication is encrypted and authenticated via pairing codes. We recommend using managed mode for most automation tasks and reserving extension relay mode only for tasks that specifically require your logged-in sessions. Never connect OpenClaw's browser to untrusted websites without reviewing the task first.

Troubleshooting Common Issues

If the browser fails to launch, check that Chromium is installed and the managed browser mode is enabled. For CDP mode, verify that Chrome is running with the remote debugging flag and the port is accessible. For the extension relay, ensure the extension is installed, the pairing code matches, and your OpenClaw Gateway is reachable from the browser. Common error messages: "Browser not found" means Chromium needs to be installed. "Connection refused" means the CDP port is not open. "Extension not connected" means the relay extension needs to be re-paired.

# Diagnostic commands
openclaw browser status     # Check browser connection
openclaw browser test       # Run a simple test page
openclaw logs --filter browser  # View browser-related logs

# Reinstall managed browser
openclaw browser install

# Reset extension relay pairing
openclaw browser relay reset

Start Automating the Web

Browser automation unlocks hundreds of new possibilities. See what others have built and get inspired.