Pricing

Open Source

Free

MIT licensed
Self-hosting on local Chrome
Full CDP access
Community support

Stealth Browsers

Custom

Managed stealth browser fleet
Anti-detection headers
No local Chrome required

Browser Use Box

Custom

24/7 always-on execution
Dedicated browser sandbox
Persistent agent sessions

Key Features

Self-healing agent loop — helpers are rewritten mid-task when they fail
Direct Chrome DevTools Protocol (CDP) integration for low-latency control
Local Chrome support for development and testing
Stealth browser fleet option to bypass bot detection
24/7 cloud execution via Browser Use Box

Pros & Cons

Pros

MIT licensed and open source — no vendor lock-in for the core harness
Self-healing design cuts brittle automation failures without manual patching
Thin CDP layer keeps overhead low compared to Playwright or Selenium wrappers
Flexible deployment: local, stealth cloud, or dedicated box

Cons

Pricing for stealth browsers and Browser Use Box is opaque — no public tiers
Requires comfort with LLM agent integration; not a no-code tool
Very new project with limited community resources and production track record
CDP-only means no Firefox or Safari support

Verdict

Browser Harness is a sharp, developer-focused primitive for building resilient browser agents — the self-healing loop that rewrites helpers mid-task is a genuinely useful idea for flaky automation. It sits one abstraction below browser-use and Playwright, which suits teams who want raw CDP control. Too early-stage and thinly documented for teams needing production SLAs today, but worth watching.

Try Browser Harness →