Fetching from the wire…
OSS2026-07-10 · source-backed
browser-use/browser-harness is a deliberately thin layer over the Chrome DevTools Protocol where the agent writes and edits its own helper functions at runtime. When it hits a missing capability (file upload is the canonical example), it edits the harness code and adds the function instead of erroring. They call it self-healing. ~15,900 stars, runs against local Chrome, stealth browsers, or a hosted Browser Use Box, with a JS sibling. The design bet: a minimal CDP bridge plus a code-writing agent beats a rigid, pre-enumerated automation API. Read it next to the TTHE paper. Same thesis, one written in C-suite prose and one in Python.
Each link below shares sources, entities, or timing with this story.
Chrome supports WebMCP / Shared entity: Chrome / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Chrome supports WebMCP); both cover Chrome; overlapping topics (agent, automation, browser, browser-use, chrome).
Google released Chrome / Shared entity: Chrome DevTools Protocol / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Google released Chrome); both cover Chrome DevTools Protocol; reported by the same outlet (github.com).
Google released Chrome / Shared entity: Chrome / Shared topic / Earlier coverage
Linked by a graph relationship (Google released Chrome); both cover Chrome; overlapping topics (agent, call, chrome).