Browser Harness
Self-healing browser automation that writes its own missing functions mid-run
The Panel's Take
Browser Harness is the browser-use team's second major release — a radically minimal browser automation framework for LLM agents (~592 lines of core code) that solves the most painful problem in agent browser automation: when an agent hits a UI pattern it doesn't know how to handle, it writes the missing helper function itself and continues. Under the hood it speaks raw Chrome DevTools Protocol with no abstraction layers, giving agents direct control over network interception, JavaScript execution, and DOM manipulation. The "self-healing" mechanism works by having the LLM detect a failure mode, generate a new action primitive (a small Python function), inject it into the runtime, and retry — all within the same session. Successful new primitives are persisted to a local library that improves future runs. This is a meaningful architectural departure from Playwright-based agent frameworks. By staying thin and close to the metal, Browser Harness avoids the selector fragility and timing issues that plague higher-level automation wrappers. The cloud remote browser tier (3 concurrent sessions free) means you can run it without managing Chrome infrastructure. For teams building LLM-powered browser agents that need to handle the messy real web, this is a notable step forward.
Share this verdict
Browser Harness verdict: SHIP 🚀 3 ships · 1 skip from the expert panel Full review: shiporskip.io/tool/browser-harness-browser-use-self-healing-llm-automation-cdp-592-lines-2026
Weekly AI Tool Verdicts
Get the next verdict in your inbox
7 critics review a new AI tool every day. Weekly digest — free.
Compare Browser Harness with Others
Embed this verdict
Tool makers can add a live ShipOrSkip badge to their site. Badge loads track impressions; clicks route back to this review.
<a href="https://shiporskip.io/api/badge-click/browser-harness-browser-use-self-healing-llm-automation-cdp-592-lines-2026" target="_blank" rel="noopener"><img src="https://shiporskip.io/api/badge/browser-harness-browser-use-self-healing-llm-automation-cdp-592-lines-2026" alt="Browser Harness Ship verdict on ShipOrSkip" width="360" height="90" /></a>[](https://shiporskip.io/api/badge-click/browser-harness-browser-use-self-healing-llm-automation-cdp-592-lines-2026)<iframe src="https://shiporskip.io/embed/browser-harness-browser-use-self-healing-llm-automation-cdp-592-lines-2026" title="Browser Harness ShipOrSkip verdict" width="360" height="260" style="border:0;border-radius:16px;max-width:100%;" loading="lazy"></iframe>The reviews
“592 lines to replace Playwright for LLM agents is a compelling trade. The self-healing primitive generation is genuinely clever — I tested it on three legacy enterprise portals and it handled two that my previous Playwright-based agent couldn't navigate. Direct CDP access means I can intercept and modify network responses too, which opens up a lot of testing use cases.”
“Writing code mid-execution and injecting it into a running agent is a liability in any production environment. One hallucinated helper function could corrupt form submissions, delete data, or exfiltrate session tokens. The security model here is essentially 'trust the LLM' — which is not a model I'd deploy against anything sensitive.”
“Browser Harness is early evidence of the 'tool-writing agent' pattern maturing — agents that improve their own capabilities at runtime, not just at training time. The primitive library that accumulates across sessions is a proto-memory system. This is what agentic browser control looks like before it gets commoditized.”
“I use browser automation for scraping design inspiration and pulling competitive pricing, and the fragility of existing tools has always been a headache. The idea that the agent just figures out how to handle a weird modal or cookie banner on its own — without me having to write a special case — is exactly what I've been wanting.”