ShipClawStealth browser
OpenClaw's anti-detection web automation layer. Patches the standard Chromium fingerprint surface that bot-detection vendors rely on. Reduces — but does not eliminate — CAPTCHA and bot-block rates.
The stealth browser is the Chromium instance OpenClaw drives when an agent needs to read a webpage, fill a form, or scrape a result. It's a patched build that hides the surface area bot-detection vendors look at: the navigator.webdriver flag, automation-only Chromium DevTools Protocol artifacts, headless rendering tells, and a few dozen other fingerprint-narrowing signals.
What it does well: routine web automation against sites that use light-touch bot detection (most blogs, marketplaces, dashboards, and SaaS apps). Form fills, link clicks, content reads, and structured scraping all just work.
What it does not do: magically defeat hard CAPTCHAs (hCaptcha enterprise, reCAPTCHA v3 with low scores), heavy fingerprint-correlation services (DataDome, PerimeterX, Kasada), or sites that gate on residential IPs. If the site requires solving an interactive puzzle, the agent will surface it back to the operator.
The stealth browser ships in every OpenClaw deployment. On ShipClaw it runs inside the same isolated container as your agent — no shared cookie jar, no cross-tenant state.