RepoRadar
Leave a Tip
Item detail

browser-use/browser-harness

Browser Harness is a fast-growing MIT-licensed browser-agent runtime that connects an LLM directly to a real Chrome session over CDP and lets the agent write the missing helpers it needs during execution.

Open source →Back to radar
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.

Who should use it

browser-agent buildersQA automation teamsworkflow prototypersAI researchers testing computer use

Who should skip it

Skip if the source link, docs, or setup requirements do not match your workflow.

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-agentcomputer-usecdpautomationchrome