Item detail
github.com

browser-use/browser-harness

browser-use/browser-harness is an AI project in RepoRadar's Radar section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 9.8 out of 10.

Score8.7
Popularity94.0
Riskconditional
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum9.0
Maturity8.7
Open-source/build8.4
Evidence7.2
Workflow potential9.8
Setup ease4.2

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

This matters because many browser agents still hide the control layer behind fixed abstractions. A thin, editable harness is more useful for teams that need real browser access, repeatable debugging, and the freedom to patch missing actions instead of waiting on a hosted platform.

Where this stands now

browser-use/browser-harness ranks #38 of 3231 tracked Radar items by composite score (8.7 against a section median of 4.9). The section currently carries 2115 Bronze, 645 Gold, 471 Silver. RepoRadar has retained observations for this record since 2026-06-18 (114 days in the current window). Signal extremes versus the section: momentum at the 92th percentile; novelty at the 85th percentile.

Who should use it

browser-agent builders QA automation teams workflow prototypers AI researchers testing computer use

Who should skip it

Consider browser-use/browser-harness lower priority if you already have a working solution in this category.

About this signal

browser-use/browser-harness is tracked by RepoRadar as an AI project in the Radar section. First seen 2026-06-18; the source record was last checked on 2026-06-18. The current verdict is 'try now' with a Gold tier and advanced setup difficulty. The standout signals for browser-use/browser-harness are workflow potential (9.8) and practical usefulness (9.0), while setup ease (4.2) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The browser-use/browser-harness record combines a 8.7/10 composite score with separate popularity (94.0), risk (conditional), and setup (advanced) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

Direct browser control can expose live sessions, uploads, and authenticated workflows if you aim it at real accounts without a sandbox profile.

Evidence links
Closest alternatives / related signals
browser-agent computer-use cdp automation chrome
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-10-10T17:09:29.745535Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

92 dated snapshots retained from 2026-06-18 through 2026-10-10; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.7 current · +0.0 net
Repository momentum9.0 current · +0.0 net
GitHub stars (observed)18,376 current · +2,444 net
GitHub stars18,376 exact observation
Versionv0.1.13
Last release2026-09-04T02:52:52Z
MaintenanceActive
Current riskConditional
Current verdictTry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-10-108.79.018,376ConditionalTry nowActive
2026-10-098.79.018,369ConditionalTry nowActive
2026-10-088.78.118,340ConditionalTry nowActive
2026-10-078.77.518,330ConditionalTry nowActive
2026-10-068.77.518,312ConditionalTry nowActive
2026-10-058.78.118,292ConditionalTry nowActive
2026-10-038.79.018,270ConditionalTry nowActive
2026-10-028.79.018,260ConditionalTry nowActive
2026-10-018.79.018,259ConditionalTry nowActive
2026-09-308.79.018,236ConditionalTry nowActive
2026-09-298.79.018,226ConditionalTry nowActive
2026-09-288.79.618,175ConditionalTry nowActive

Why the record changed

Stars change

Stars changed: 18365 → 18376.

Stars change

Stars changed: 18369 → 18365.

Stars change

Stars changed: 18362 → 18369.

Stars change

Stars changed: 18340 → 18362.

Stars change

Stars changed: 18330 → 18340.

Stars change

Stars changed: 18318 → 18330.

Stars change

Stars changed: 18312 → 18318.

Stars change

Stars changed: 18304 → 18312.

Stars change

Stars changed: 18292 → 18304.

Stars change

Stars changed: 18270 → 18292.

Stars change

Stars changed: 18267 → 18270.

Stars change

Stars changed: 18260 → 18267.