The right browser for OpenClaw, laptop or server.

On your laptop, OpenClaw's own browser is free. On a VPS or in Docker, use a node host on a machine with Chrome, or a hosted stealth browser with one cdpUrl. Browser Use Cloud is $0.06 per browser-hour, no subscription.

{  browser: {    enabled: true,    defaultProfile: "browser-use",    profiles: {      "browser-use": {        cdpUrl: "wss://connect.browser-use.com?apiKey=<BROWSER_USE_API_KEY>&proxyCountryCode=us",      },    },  },}
~/.openclaw/openclaw.jsonOpenClaw remote CDP profile
OpenClaw's own local browser, when OpenClaw runs on your laptop
Free
Browser Use Cloud on a VPS or in Docker; residential proxy $5/GB, no subscription
$0.06 / hour
got through on Stealth Bench V2, sites picked where Browser Use Cloud historically got through, so not a balanced sample; next best Anchor 82%
90.5%

How do I give OpenClaw a browser that doesn't get blocked?

As of Nov 2, 2026: what each option does against blocks out of the box, with the cdpUrl from its own OpenClaw guide. None gets through everywhere. OpenClaw's docs also list Notte, not covered here.
OpenClaw's own browser: Setup: openclaw browser start, or a node host on a machine with Chrome; Stealth: Your real Chrome, with the user or chrome profile; Proxy and CAPTCHA: That machine's IP. No CAPTCHA solver.; Price: Free;
Browserless: Setup: wss://production-sfo.browserless.io?token=<TOKEN>; Stealth: Opt-in: the /stealth route; Proxy and CAPTCHA: Opt-in: proxy=residential (6 units/MB), solveCaptchas=true (10 units a solve, hosted only); Price: Free: 1,000 units/month (unit = 30 s), 2-min sessions. From $25/month, billed yearly.;
Browserbase: Setup: wss://connect.browserbase.com?apiKey=<KEY>; Stealth: Not on Free. Basic from $20/month; Advanced and Verified on Scale (sales); Proxy and CAPTCHA: From $20/month: proxy off by default, CAPTCHA solving on. Neither on Free.; Price: Free: 1 hour, 15-min sessions. $20/month: 100 hours, then $0.12/hour; 1 GB proxy, then $12/GB.;
Browser Use Cloud: Setup: wss://connect.browser-use.com?apiKey=<KEY>&proxyCountryCode=us; Stealth: On by default; Proxy and CAPTCHA: Both on by default, proxy in 195+ countries. EU region: no CAPTCHA solving.; Price: $0.06/hour + $5/GB proxy. Sessions up to 240 min. No subscription.;

Sources: OpenClaw: profiles, remote browsers, troubleshooting, Browserless: OpenClaw guide, stealth, proxies, CAPTCHAs, pricing, Browserbase: OpenClaw setup, Verified, proxies, CAPTCHAs, pricing, Browser Use: OpenClaw guide, stealth and proxies, CAPTCHAs, pricing, checked Nov 2, 2026.

Laptop or server?

On your own laptop, use OpenClaw's built-in browser. The openclaw profile is a separate local browser; the user and chrome profiles drive your real signed-in Chrome (OpenClaw docs). It costs nothing, and sites see your IP. On a VPS or in Docker, the server has no signed-in Chrome and sites see its IP. If a machine with Chrome stays on, run an OpenClaw node host there and the Gateway sends browser actions to it (OpenClaw docs). If not, or you need many parallel sessions or residential IPs, point a browser profile at a hosted browser: with Browser Use, the cdpUrl carries a residential proxy country, CAPTCHA solving is on, and a saved profile brings your logins (guide).
Where OpenClaw runs decides the browser
On your laptop
OpenClaw's local browserFree. Sites see your IP. The user and chrome profiles drive your signed-in Chrome.
Server, plus a machine with Chrome
An OpenClaw node hostFree. The Gateway sends browser actions to the node host's Chrome, on that machine's IP.
Server only
A hosted stealth browserOne cdpUrl. When no machine with Chrome stays on, or you need many parallel sessions or residential IPs. Browser Use Cloud: $0.06 per hour, proxy $5/GB.

What a hosted browser costs.

Browser Use Cloud is $0.06 per browser-hour, billed by the minute, plus $5/GB of residential proxy traffic. No subscription. A session runs at most its timeout, set in minutes in the cdpUrl. Pricing.

Which gets blocked least?

On Stealth Bench V2, Browser Use Cloud got through on 90.5% of visits to 100 bot-protected sites; the next best, Anchor, on 82%. Each provider ran with its own managed proxy and CAPTCHA solver, plus whatever stealth its plan includes. Steel's stealth browser needs its Enterprise plan and Browserbase's Verified mode its Scale plan; neither was used. 17 of Browserless's 200 visits were unresolved and count as not through; had all got through it would be 86%, and an independent rerun put it at 83%. One caveat: the 100 sites were picked because Browser Use Cloud historically got through where stock Chrome with a US proxy did not. They are hard on purpose and not a balanced sample of the web or of anti-bot vendors. Method, code and raw results.
Got through, Stealth Bench V2
  1. 1Browser Use Cloud90.5%
  2. 2Anchor82%
  3. 3Kernel80.5%
  4. 4Browserbase78.5%
  5. 5Browserless17 visits unresolved; up to 86%, rerun 83%77.5%
  6. 6Steel74.5%
  7. 7Hyperbrowser73.5%

Keep OpenClaw logged in.

Run the profile sync helper on your laptop to copy a login from your Chrome into a Browser Use profile. Add its id to the cdpUrl as profileId. The server's browser starts with those cookies, and no password goes into the prompt. Re-sync when the site's login expires.

cdpUrl parameters

apiKey
Your Browser Use API key. Required.
proxyCountryCode
Country of the residential proxy, for example us, de or jp.
profileId
A saved browser profile with cookies and localStorage.
timeout
Session length in minutes, up to 240. Caps how long one session can run.

Questions people ask

Which browser should OpenClaw use?

On your own laptop, use OpenClaw's built-in local browser: it is free, sites see your own IP, and its user and chrome profiles use your signed-in Chrome. On a VPS or in Docker, either run an OpenClaw node host on a machine that has Chrome, or point a browser profile at a hosted stealth browser with one cdpUrl. Browser Use Cloud costs $0.06 per browser-hour plus $5/GB for residential proxy traffic, and got through on 90.5% of visits on Stealth Bench V2, against 82% for Anchor, the best of six other providers (sites picked where Browser Use Cloud historically got through, so not a balanced sample).

How do I connect OpenClaw to Browser Use?

Add a browser profile to ~/.openclaw/openclaw.json whose cdpUrl is wss://connect.browser-use.com?apiKey=<BROWSER_USE_API_KEY>&proxyCountryCode=us, and set it as defaultProfile. OpenClaw then runs its browser commands, such as openclaw browser open, snapshot and screenshot, on a Browser Use cloud browser. No SDK is needed. The config is in both the Browser Use OpenClaw guide and OpenClaw's remote browser docs.

Does OpenClaw need a cloud browser?

No. On your own computer, OpenClaw's built-in openclaw profile runs a separate local browser, and its user and chrome profiles drive your real signed-in Chrome. That costs nothing and sites see your own IP. When OpenClaw runs on a VPS or in Docker, you can run an OpenClaw node host on a machine that has Chrome, and the Gateway sends browser actions to it. A hosted browser fits when there is no always-on machine with Chrome, you need many parallel sessions, or you need residential IPs and stealth.

How do I keep OpenClaw logged in to a site?

Sync a login from your local Chrome into a Browser Use profile with the profile sync helper, then add profileId=<PROFILE_ID> to the cdpUrl. The browser starts with the synced login cookies, so no password goes into the prompt. Re-sync when the site's login expires; some sites bind sessions to a device or network.

What does a hosted browser for OpenClaw cost?

On Browser Use Cloud, $0.06 per browser-hour, billed by the minute, plus $5/GB of residential proxy traffic. No subscription. A session runs at most its timeout, set in minutes in the cdpUrl.

Which hosted browser gets blocked least?

On Stealth Bench V2, every hosted browser tested: Browser Use Cloud 90.5%, Anchor 82%, Kernel 80.5%, Browserbase 78.5%, Browserless 77.5%, Steel 74.5%, Hyperbrowser 73.5%. Share of 200 scheduled visits (100 sites × 2 runs) where a judge model, shown the page without the provider name, confirmed the real site loaded within 60 seconds. Each provider ran with its own managed proxy and CAPTCHA solver, plus whatever stealth its plan includes. Steel's stealth browser needs its Enterprise plan and Browserbase's Verified mode its Scale plan; neither was used. 17 of Browserless's 200 visits were unresolved and count as not through; had all got through it would be 86%, and an independent rerun put it at 83%. The 100 sites were picked because Browser Use Cloud historically got through where stock Chrome with a US proxy did not. They are hard on purpose and not a balanced sample of the web or of anti-bot vendors. Code and raw results are public.

Is the site blocking OpenClaw, or OpenClaw itself?

A 403 or a challenge page is the site; another browser or proxy can help. If start and tabs work but open or navigate fails with a policy error, it is usually OpenClaw's own SSRF policy (browser.ssrfPolicy), which by default blocks private addresses; another browser won't fix that. See OpenClaw's troubleshooting docs.

Can I self-host the browser?

Browser Use Cloud is hosted by default, with an EU region. On-prem deployment of browsers and agents is available to enterprise customers through sales. Browserless can run in Docker next to OpenClaw; OpenClaw's docs show that setup with attachOnly: true. Self-hosted Browserless is free for non-commercial use; commercial use needs a license (SSPL-1.0 or a commercial license). Steel's steel-browser (Apache-2.0) is open source and runs in Docker too. Kernel publishes its browser image (Apache-2.0) to run in Docker, separate from its hosted service.