Option 1: Cloud Browser via CDP
OpenClaw has a built-in browser tool with its own CLI commands (openclaw browser). By default, it controls a local Chromium instance. You can point it at a Browser Use cloud browser instead by configuring a remote CDP profile.
Browser Use exposes a WebSocket CDP URL. OpenClaw connects to it like any remote browser — no SDK or extra dependencies needed.
Setup
1. Get your API key Sign up at cloud.browser-use.com and copy your API key from Settings → API Keys. 2. Add a Browser Use profile Open~/.openclaw/openclaw.json and add a browser-use profile:
<BROWSER_USE_API_KEY> with your actual key. All Browser Use session parameters can be passed as query params in the cdpUrl:
timeout— session duration in minutes (max 240)profileId— load a saved browser profile with persistent cookies and localStorageproxyCountryCode— route traffic through a specific country (e.g.us,de,jp)
defaultProfile to "browser-use" in the config (as shown above), you can drop the --browser-profile flag:
Option 2: Browser Use CLI
The Browser Use CLI is a standalone tool that gives any OpenClaw agent browser automation through a SKILL.md file. The agent reads the skill and learns to use the CLI commands directly. It’s available on skills.sh and ClawHub.Setup
1. Install the CLIbrowser-use CLI to navigate pages, click elements, fill forms, take screenshots, extract data, and more. The skill file teaches the agent the full command set.
For the complete CLI reference and advanced features like cloud browsers, tunnels, sessions, and Python execution, see the README and the Browser Use docs.