Browser Harness adds self-healing browser automation

The interesting part here is less “browser automation” and more “agent runtime that can repair itself.” That makes it a sharper bet than selector-heavy frameworks, but also a more opinionated one: it assumes the agent is allowed to edit its own tooling as it goes.

• –CDP-first design keeps the stack thin and close to the browser, which should help with reliability and lower overhead versus heavier abstraction layers.
• –Self-healing behavior is the real differentiator: when a site shifts or a modal blocks progress, the agent can write the missing interaction rather than fail hard.
• –The repo framing suggests this is aimed at power users and agent builders, not no-code automation customers.
• –The “skills” and helper-based workflow points toward reusable browser task primitives, which is useful if you want agents that get better at a domain over time.
• –This sits squarely in the growing browser-agent tooling race alongside Browser Use, Stagehand, and similar projects, but with a more hackerish, inspectable feel.