OSS
browser-use Ships 'Browser Harness' — Agents Edit Their Own Browser Helpers Mid-Task Instead of Failing
browser-use/browser-harness is a deliberately thin layer over the Chrome DevTools Protocol where the agent writes and patches its own helper functions at runtime. When it hits a missing capability mid-task — file upload is the canonical example — it edits the harness code and adds the function rather than erroring out, which the project calls 'self-healing.' It runs against local Chrome, stealth browsers, or a hosted Browser Use Box, is at ~15.9K stars, and now has a JS sibling (browser-harness-js). The design bet is that a minimal CDP bridge plus a code-writing agent beats a rigid, pre-enumerated automation API.
Source
↳ Follow the thread