What did Hlido score browser-use/browser-harness?

browser-use/browser-harness scored 40/100 (FADING) in Hlido's independent, hands-on review.

Is browser-use/browser-harness reliable?

browser-use/browser-harness is rated FADING (40/100) by Hlido. Alpha-stage self-healing browser harness from the browser-use project — technically interesting for LLM-driven automation, but too early for production evaluation.

How much does browser-use/browser-harness cost?

Hlido recorded the pricing model as: Open source. Derived from evidence Hlido holds, not vendor-supplied; verify current prices on the vendor's pricing page.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

browser-use/browser-harness

Name: browser-use/browser-harness review
Item: browser-use/browser-harness
Rating: 40
Author: Hlido Editor

AI Agent · tested 2026-06-07 · re-test due 2026-09-07 · by the Hlido desk, not the vendor

In short: An alpha-stage self-healing browser harness from the browser-use project — interesting technical thesis for LLM-driven browser automation, but too early to evaluate as a production tool.

Visit browser-use/browser-harness → scorecard.json

Quick answer

browser-use/browser-harness scores 40/100 (FADING) on Hlido’s independent, hands-on test (reviewed 2026-06-07). FADING (40) because the project is at GitHub-only alpha stage: no product site, no documentation, no changelog, no API contract stability, and no evidence of production usage. Pricing: Open source (free entry point documented).

Hlido Editor · 2026-06-07

browser-harness is a GitHub project under the browser-use organisation — the same team behind the browser-use Python library that gained significant attention in 2024-25 for enabling LLMs to control browsers. The harness is described as a 'self-healing harness that enables LLMs to complete any task', which suggests it sits above the core browser-use library as an abstraction layer that handles selector drift and site changes automatically. At the time of review, the GitHub repository is the only surface: there is no dedicated product page, no documentation site, no pricing (it appears to be open source), and no changelog. The self-healing concept is genuinely useful for production browser automation — anyone who has run Playwright scripts against real websites knows the maintenance burden of selectors breaking. But this project does not yet have the documentation depth, release stability, or usage evidence to earn a higher score. The browser-use core library is the mature sibling; this harness is an experiment adjacent to it.

Why FADING

FADING (40) because the project is at GitHub-only alpha stage: no product site, no documentation, no changelog, no API contract stability, and no evidence of production usage. The concept is sound (self-healing browser harness) but the surface does not yet support a higher evaluation.

What we saw

1 screenshot captured by the Hlido engine during the reviewed run (run-f54f1ab6a79fd5f4-browser-harness-com). Our own captures — not vendor marketing material.

browser-use/browser-harness — run screenshot 1 (home.png) — home.png

What it does well

Self-healing selector approach addresses a genuine pain point in browser automation maintenance
Part of the browser-use ecosystem which has real community momentum
Open source — no cost barrier to evaluation

What it fails at

GitHub-only surface — no product page, docs site, or release notes
No versioned releases or stability guarantees
No usage examples or integration guides in the repository
Changelog not found in automated audit
Cannot evaluate production readiness from public surface

Red flags

No documentation, versioned releases, or stability signals at time of review — evaluate only for experimental or research use.

Best for

Researchers and early adopters experimenting with LLM-driven browser automation stacks
browser-use users who want to extend the library with self-healing capabilities

Not recommended for

Production browser automation workflows requiring stability guarantees
Teams without Playwright/Python browser automation experience
Anyone needing documentation, support, or stable API contracts

Pricing & access

ModelOpen source
Free entry pointYes — a free tier or open-source edition is documented

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-06-04.

Compared to

browser-use/browser-use production-readiness
browser-use (the core library) is the mature sibling — documented, actively maintained, and production-used. browser-harness is an experimental alpha layer above it. Start with the core library.

Agent relevance

SDK Behavioral-testable

Agentic-Commerce Readiness 28/100 · SURFACE-ONLY

Independent readiness for agent delegation & transaction. How it’s scored · check live

Open source Python project — an agent system could install and use it as a library for browser automation tasks. No stable API contract yet; use as an experimental component only. The self-healing concept makes it relevant for LLM-driven agents that need browser interaction.

Agent-friendly score: 5/10

Evidence

GitHub repository accessible — source (2026-06-04) verified
Self-healing browser harness description — source (2026-06-04) verified

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-09-07

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/browser-use-browser-harness.svg)](https://hlido.eu/check/?agent=browser-use-browser-harness)

HTML

<a href="https://hlido.eu/check/?agent=browser-use-browser-harness"><img src="https://hlido.eu/badge/browser-use-browser-harness.svg" alt="Hlido trust score"></a>