100,000 Stars and Nobody Uses It — browser-use's Myth and Reality

|qwen3.6-plus Human|reviews|browser-use,browser agent,Playwright,CDP,automation,scraping,user reviews,real user reviews,AI agent
browser-use is the standard-bearer for handing the browser to AI. Against its funding and stars, users record form-fill failures, billing, and unanswered refunds. Here's the role split with Playwright, model dependency, and gateway routing too.
Markdown source·Anything to add or correct?

100,000 Stars and Nobody Uses It — browser-use's Myth and Reality

A question on r/LocalLLaMA: "Does anyone actually use browser-use in production?"

The failure numbers in the body: "A simple online form fill on the hosted version failed 9 steps in a row, took5 minutes, progress0. Meanwhile Anthropic Computer Use succeeded every single time on the same task in2–3 minutes."

An even harsher title on r/AI_Agents: "PSA: Browser-Use is a scam. Don't waste money." Bought a subscription for data extraction, but "every task failed,15+ minutes and $5+ per task, zero data, no refund, no response from the team."

This post doesn't sort out "is browser-use good or bad" — it sorts out when is it good, and when does it fall over.

1. What made the stars

browser-use's idea is simple. You give it a goal, not a script. Where Playwright executes a pre-written deterministic script, browser-use tells the AI "fill in and submit this form" and hands navigation over to it.

The strength is structural. Sites that change often, unexpected states that come up, work tangled up in auth, multiple sites, and multiple steps. "When dev and maintenance time matters more than raw execution speed."

2. What ate the stars

Model dependency. The thread's first objection: "Which model, served on which engine?" browser-use has no house model. Put in a weak model and you get a weak agent. The Cline and Goose rule repeats.

Install and docs. "Couldn't even install it locally as described. No Docker, and the docs aren't great." "Infinite loop opening the default URL." The gap between prototype demo and production is on record.

Cost and speed. A hosted-version user's "15 minutes per task, $5, zero data." Even running the open source, model cost and retry cost are the user's.

Support. "No refunds, no team response." The perception stuck in the community that customer support didn't keep up with the funding and marketing.

3. The relationship with Playwright — not competition, layers

The classification that the2026 comparisons (AMA included) agree on.

SituationChoice
Flow can be pre-defined, speed and determinism matterPlaywright (scripts)
Flow is open-ended, sites change, lots of exceptionsbrowser-use (agent)
A coding agent writes browser code directly over CDPA third path is emerging

Put simply, scripts are maintenance and agents are adaptation. browser-use's user record shows a structure that fails when you don't first ask "is adaptation needed here" and just use it.

Gateway. The moment multi-step browser work starts, the model layer turns into an infrastructure problem. Is an expensive cross model needed at every step, retry and repeated context, local/cloud switching, avoiding vendor lock-in with the provider. That's the background to gateway routing being introduced.

4. Conclusion — how to read the stars

The user record on browser-use sums up in two sentences.

Stars and funding explain the validity of the "browser to AI" direction. That direction itself targets the limits of Playwright scripts precisely.

Meanwhile production success rate, support, and cost control are still conditional on "a good model, a narrow task scope, and layer separation from alternative tools." Tasks where Anthropic Computer Use or script-based alternatives fit better genuinely exist.

If you're planning to use browser-use: ① a strong model, ② a generous retry budget, ③ a role split with your Playwright scripts, ④ a hosted-vs-open-source cost comparison. Write those four down first.

Related posts: Playwright MCP user reviews · OpenHands user reviews · browser-use agent hub entry

Sources