---
title: "OpenClaw browser: local Chrome or a hosted stealth browser"
description: "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)."
canonical: "https://browser-use.com/openclaw"
last_updated: "2026-11-12"
---

# OpenClaw browser: local Chrome or a hosted stealth browser

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

[HTML page](https://browser-use.com/openclaw) · [Browser Use OpenClaw guide](https://docs.browser-use.com/cloud/tutorials/integrations/openclaw) · [OpenClaw remote browser docs](https://docs.openclaw.ai/tools/browser/remote#browser-use) · [Cloud browsers compared](https://browser-use.com/cloud-browsers.md) · [Residential proxies](https://browser-use.com/proxies.md)

## 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](https://docs.openclaw.ai/tools/browser/remote#notte), not covered here.

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

Sources: [OpenClaw: profiles](https://docs.openclaw.ai/tools/browser/profiles), [remote browsers](https://docs.openclaw.ai/tools/browser/remote), [troubleshooting](https://docs.openclaw.ai/tools/browser/troubleshooting), [Browserless: OpenClaw guide](https://docs.browserless.io/ai-integrations/open-claw), [stealth](https://docs.browserless.io/baas/bot-detection/stealth), [proxies](https://docs.browserless.io/baas/bot-detection/proxies), [CAPTCHAs](https://docs.browserless.io/baas/bot-detection/captchas), [pricing](https://www.browserless.io/pricing), [Browserbase: OpenClaw setup](https://docs.browserbase.com/integrations/openclaw/setup), [Verified](https://docs.browserbase.com/platform/identity/overview), [proxies](https://docs.browserbase.com/platform/identity/proxies), [CAPTCHAs](https://docs.browserbase.com/platform/identity/captcha-solving), [pricing](https://www.browserbase.com/pricing), [Browser Use: OpenClaw guide](https://docs.browser-use.com/cloud/tutorials/integrations/openclaw), [stealth and proxies](https://docs.browser-use.com/cloud/browser/stealth), [CAPTCHAs](https://docs.browser-use.com/cloud/browser/captcha-handling), [pricing](https://browser-use.com/pricing); checked Nov 2, 2026.

Still blocked? 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](https://docs.openclaw.ai/tools/browser/troubleshooting).

## Laptop or server?

- **On your laptop**: OpenClaw's local browser. Free. The `openclaw` profile is a separate local browser; the `user` and `chrome` profiles drive your real signed-in Chrome. Sites see your IP. [OpenClaw profiles](https://docs.openclaw.ai/tools/browser/profiles)
- **On a VPS or in Docker, plus a machine with Chrome**: run an OpenClaw node host on that machine and the Gateway sends browser actions to its Chrome, on its IP. Free. [OpenClaw node browser proxy](https://docs.openclaw.ai/tools/browser/remote#node-browser-proxy-zero-config-default)
- **On a VPS or in Docker, server only**: the server has no signed-in Chrome and sites see its IP. Point a browser profile at a hosted browser; this also fits many parallel sessions or a need for residential IPs. With Browser Use, the cdpUrl carries a residential proxy country, CAPTCHA solving is on, and a saved profile brings your logins.

## Config

Add a profile to `~/.openclaw/openclaw.json`:

```json5
{
  browser: {
    enabled: true,
    defaultProfile: "browser-use",
    profiles: {
      "browser-use": {
        cdpUrl: "wss://connect.browser-use.com?apiKey=<BROWSER_USE_API_KEY>&proxyCountryCode=us",
      },
    },
  },
}
```

Then:

```bash
openclaw browser open https://example.com
openclaw browser snapshot
openclaw browser screenshot
```

cdpUrl parameters, from the [Browser Use OpenClaw guide](https://docs.browser-use.com/cloud/tutorials/integrations/openclaw) and [OpenClaw's remote browser docs](https://docs.openclaw.ai/tools/browser/remote#browser-use):

| Parameter | Meaning |
|---|---|
| `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. |

## Keep OpenClaw logged in

Run the [profile sync helper](https://docs.browser-use.com/cloud/guides/profile-sync) on your laptop to copy a login from your Chrome into a Browser Use profile, then add `&profileId=<PROFILE_ID>` to the cdpUrl. The server's browser starts with those cookies, and no password goes into the prompt. Re-sync when the site's login expires; some sites bind sessions to a device or network.

## What a hosted browser costs

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`. [Pricing](https://browser-use.com/pricing.md)

## Which gets blocked least?

Stealth Bench V2, share of visits that got through, 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%. 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%. 200 visits (100 bot-protected sites, 2 runs), judged blind. 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](https://browser-use.com/benchmarks/browsers)

## Can I self-host the browser?

Browser Use Cloud is hosted by default, with an [EU region](https://docs.browser-use.com/cloud/eu-deployment). On-prem deployment of browsers and agents is available to enterprise customers [through sales](https://browser-use.com/enterprise#talk-to-sales). Browserless can run in Docker next to OpenClaw; [OpenClaw's docs](https://docs.openclaw.ai/tools/browser/remote) show that setup with `attachOnly: true`. [Self-hosted Browserless](https://github.com/browserless/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.

---

BROWSER USE

- Browser Use Agents: give Browser Use a task and receive completed work. API V4 is current for new integrations.
- Browser Infrastructure: connect your agent or automation to managed browsers through SDK, REST, or CDP. Starts at $0.06/browser-hour.
- Developer tools: Open Source, Browser Harness, SDK, and MCP support the two products above.

[Developer Index](https://browser-use.com/index.md)
[Product Map](https://browser-use.com/llms.txt)
[Full Product Context](https://browser-use.com/llms-full.txt)
[Pricing](https://browser-use.com/pricing.md)
[Cloud Docs](https://docs.browser-use.com/cloud/quickstart)
[Open Source Docs](https://docs.browser-use.com/open-source/introduction)
