AI tool comparison
Browser Harness vs Windmill
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Browser Automation
Browser Harness
Self-healing browser agent that writes its own missing capabilities mid-task
75%
Panel ship
—
Community
Free
Entry
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.
Automation
Windmill
Open-source developer platform for scripts and workflows
100%
Panel ship
—
Community
Free
Entry
Windmill turns scripts into workflows, UIs, and scheduled jobs. Write in TypeScript, Python, Go, or SQL and get auto-generated UIs with approval flows.
Reviewer scorecard
“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.”
“Scripts become workflows with auto-generated UIs. The approval flows and scheduling turn scripts into proper automation.”
“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.”
“Open-source Retool + n8n hybrid. The auto-generated UI from script parameters is surprisingly useful.”
“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.”
“Internal tooling from scripts with auto-generated UIs is the right abstraction for developer-built automation.”
“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.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.