Browser Use review

Browser Use is a hosted browser-agent and cloud-browser service, alongside Browser Harness, a free, open-source browser tool for Claude Code and Codex. The hosted agents accept a task and return JSON; the cloud browsers provide a browser environment designed to get past bot checks. Browser Harness is a separate integration surface for coding agents.

In a stack, Browser Use sits between an agent or application and the websites it needs to operate. The agent supplies the goal, Browser Use provides browser control, and the result can feed back into application logic. That differs from a fixed automation script: the agent decides how to carry out a task, so page changes and model decisions can affect outcomes. The vendor lists US or EU cloud, with EU runs in Frankfurt, and on-prem deployment for enterprise. It also lists SOC 2 Type II and HIPAA on enterprise plans.

The homepage describes a task-based web-agent interface: send a task and receive JSON. It also advertises stealth browsers and shows Browser Harness operations such as new_tab, click_at_xy and js. Browser Harness is positioned for Claude Code and Codex, and the homepage says it is used as the browser tool in Hermes Agent.

The homepage does not name a programming language, SDK, API protocol, CLI or webhook. Treat the task-to-JSON agent and Browser Harness as the published integration surfaces, and confirm SDK support, authentication, request and response schemas, and documentation details in the vendor’s docs before choosing a language or designing an adapter. The vendor advertises a $0.006-per-task web-agent price, but buyers should confirm which model and execution costs that task rate covers. For a production integration, also ask about retries, timeouts, idempotency, logs and how task results are retrieved.

Pay as you go costs $0 per month, with a $1 one-time signup credit. The plan includes up to 1,000 browsers at once, credits that never expire, SOC 2 Type II and a signed DPA. There is no subscription or annual billing. Browser Harness is free and open source, but it is a separate tool rather than a stated allowance of hosted browser usage.

Hosted usage adds up by resource: browser time costs $0.02 per hour, billed by the minute with a one-minute minimum; home-IP traffic is $5/GB, while direct or your own proxy is $0.20/GB. BU Ultrafast is $0.006 per task. Agent models are billed at varying per-token rates, or a bring-your-own key costs the provider rate plus 0.2x. The vendor lists paid concurrency thresholds: $100 total paid for 50 browsers, $1,000 for 250, $5,000 for 500 and $25,000 for 1,000. Enterprise has custom pricing, annual credit pools and custom concurrency above 1,000.

Browser Harness is described as free and open source, but the homepage does not name its licence. Check the repository’s licence before redistributing or embedding it in a product. The hosted web agents and cloud browsers are a separate service; the homepage lists on-prem deployment as an enterprise option, not as a self-serve installation path.

The vendor does not publish data-export or migration details on the homepage. Ask whether task inputs, JSON results, browser recordings and logs can be exported, how long they are retained, and whether an on-prem deployment changes those terms. Browser Harness may offer a more portable integration point than depending on hosted browser sessions, but the agent, model billing and browser infrastructure can still create service-specific dependencies. Confirm the supported export formats and what happens to stored data when an account closes.

The vendor lists up to 1,000 concurrent browsers on Pay as you go, with higher custom concurrency on Enterprise. It does not publish request-rate limits or detailed retry and availability targets on the homepage; ask for those, plus the applicable SLA, before placing time-sensitive work on the service. Costs can include browser minutes, IP traffic and model tokens, not just the task rate.

Browser Use lists SOC 2 Type II and a signed DPA on Pay as you go, with HIPAA available on enterprise plans. Confirm the data-handling terms for your workload, and whether your deployment region and retention requirements are supported. Reddit feedback is mixed: one commenter praised varied tasks and CAPTCHA handling in the Web UI, while a separate thread describes hallucinated clicks and sessions that fail. Treat those as user reports, not service guarantees. Test retries, page changes, authentication and failure recovery against your own sites.