Browser Use friction hits production scraping

This is less a product launch story than a market signal: teams are starting to split “AI browser agents” into two camps, demo-friendly autonomy and production-grade control.

• –The complaint matches Browser Use’s own positioning: its open-source agent is powerful, but the company now heavily pushes cloud infrastructure, stealth browsers, custom models, and Skill APIs for production workloads
• –The thread highlights the core tradeoff in agentic browsing today: full-step autonomy reduces scripting effort up front, but latency, token cost, and error recovery can explode once workflows get repetitive and high volume
• –Stagehand keeps coming up because its act/extract/observe model gives developers tighter control over execution, which is exactly what production scraping teams usually want
• –The subtext is that many teams are drifting toward hybrid stacks: deterministic Playwright for known flows, AI only where DOM ambiguity or fuzzy matching actually justifies the cost
• –For AI developer tooling, that makes Browser Use notable not just as a library, but as an early test case for where autonomous browser agents stop being magic and start needing workflow engineering