Browser Harness
Self-healing browser agent that writes its own missing capabilities mid-task
The Panel's Take
Browser Harness is a radically minimal Python framework from browser-use that gives LLMs autonomous control over Chrome via the Chrome DevTools Protocol (CDP). The entire codebase is around 592 lines across five files — and that minimalism is intentional. The philosophy: don't constrain the agent with pre-built recipes. Instead, let it identify what's missing and write new domain-skill files on the fly. When the agent hits a capability gap mid-task (say, a tricky CAPTCHA flow or a site with unusual navigation patterns), it authors the missing handler itself and stores it in a domain-skills directory for future runs. Over time, the harness self-improves, accumulating institutional knowledge about specific websites. It also ships with remote browser support — three free concurrent cloud instances — removing the local setup burden. The "Show HN" debut generated early traction for what is fundamentally a different philosophy from frameworks like Playwright or Selenium: instead of comprehensive APIs that try to anticipate every scenario, Browser Harness trusts the LLM to extend itself. This is either the future of browser automation or a maintenance nightmare — probably both.
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-cdp-chrome-mit-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-cdp-chrome-mit-2026" target="_blank" rel="noopener"><img src="https://shiporskip.io/api/badge/browser-harness-browser-use-self-healing-llm-cdp-chrome-mit-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-cdp-chrome-mit-2026)<iframe src="https://shiporskip.io/embed/browser-harness-browser-use-self-healing-llm-cdp-chrome-mit-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 of Python is the most impressive part. The self-healing skill-file approach means it gets better the more you use it on a specific site, without any manual intervention. For internal tooling against well-known sites, this is a legitimate alternative to maintaining a brittle Playwright script.”
“An agent that writes its own code mid-task is powerful but auditably scary. What exactly is getting written to those domain-skill files? For anything touching auth flows, financial sites, or sensitive data, you want deterministic, reviewable automation — not self-modifying LLM-authored scripts. Pre-alpha warning is warranted.”
“The principle here — give agents the freedom to extend themselves rather than boxing them into predefined APIs — is the correct long-term direction. Every browser automation framework eventually becomes a sprawling collection of edge-case handlers. Starting from minimal and letting the agent accumulate domain knowledge is cleaner architecture.”
“For content workflows that involve repetitive browser tasks — scraping competitor sites, pulling analytics, posting to platforms — a self-improving agent that handles edge cases better each time sounds genuinely useful. I'd try it on low-stakes automation first and see how the skill files look.”