You think the agent finished the reimbursement until you open the trace. It gathered receipts, bank lines, and policy PDFs for hundreds of steps, opened ExpenseFlow at step 459, and at step 500 was still reverse-engineering a calendar picker. It never submitted. That is Task008 on OSWorld 2.0: 108 long-horizon workflows, a published top of 20.6 percent binary completion and a 54.8 percent partial score for Claude Opus 4.8 with max thinking and batched tools in the OSWorld 2.0 paper, and 0 percent binary completion past 163 minutes (that cutoff is on the OSWorld 2.0 site).
The buying problem is older than the benchmark. Vendor portals and ten-page government forms still have no API, and a Playwright selector dies the day .submit-btn becomes .btn-primary-v2. Four products we would actually run in 2026: Browser Use, Skyvern, Browserbase with Stagehand, and Anthropic Computer Use. What we checked this week (18 Aug 2026): official changelogs, the four homepages, OSWorld, and the papers. That is the first-party layer we have.
The cost of using a frontier model as a clicker is not a lab complaint. On Show HN: Smooth CLI (109 points, 74 comments when we opened it on 18 Aug 2026), the OP put it in one line:
Using a giant general-purpose model like Opus to click on buttons and fill out forms ends up being slow and expensive.
Same thread, same problem: agents “don’t handle the billion edge cases of the internet like iframes nested in iframes nested in shadow-doms.”
On r/LocalLLaMA (12 Feb 2026), someone running Browser Use in production said the quiet part:
I'm not sure how many people know about browser-use but we have an app powered by browser-use and it's working pretty well. It's not super fast but it always finds stuff within 1min.
Browser Use
An MIT-licensed Python library plus a hosted cloud that turns a website into something an LLM can drive: click, type, extract, retry when the layout moves. pip install is the open-source path. The commercial path is a Hosted Agents API and managed browsers. Magnus Müller and Gregor Žunič founded it in 2024 out of ETH Zurich. Y Combinator W25, then a $17 million seed in March 2025 led by Felicis.
The cloud side moved in public this summer. On 17 Jul 2026 the Browser Harness (v4) agent API became public, and the pay-as-you-go top-up minimum dropped from $25 to $5. On 10 Aug: session sharing at /share/v4, X402 pay-what-you-want top-ups from $0.01 to $100, free polling / reading / stopping of an already-open session, and per-run cost caps up to $100. The library hit 0.13.8 on 16 Aug 2026.
Best for:
Engineering teams that want an MIT-licensed agent loop they can self-host, then move the same idea onto managed browsers when proxies, concurrency, or stealth become the bottleneck.
Key Features:
- The 17 Jul changelog added Hosted Agents API V4 / Browser Harness, with configurable per-run spend caps.
- Managed browsers with stealth, CAPTCHA handling, and proxies in 195-plus countries, billed from $0.02 per browser-hour.
- The open-source Python library runs against your own browsers and model keys.
- Deterministic replay, so a successful path can be re-run without a full agent loop every time.
Why we like it:
The only product here that is both a serious open-source agent library and a priced cloud with published browser-hour and proxy rates. Start local, then buy infrastructure when the local browser becomes the problem.
Notable Limitations:
- The company says the hosted product is stronger than the library, so a local prototype is not proof the same task holds without the cloud extras.
- An independent review in 2026 still flags flaky runs and token cost on long workflows. For stable scraping, Playwright is cheaper.
- Stealth and CAPTCHA extras live on the cloud path. The library does not inherit them.
Pricing:
Published. Free: 10 agent tasks per month, 3 concurrent sessions. Pay-as-you-go credits, $5 top-up floor. Dev $29, Business $299, Scaleup $999. Browsers still $0.02 per browser-hour. Residential proxy $5/GB. You still pay model tokens on the open-source path.
Skyvern
A vision-first workflow product for portal work that has no usable API. Skyvern takes a screenshot, finds the control that looks like the button you meant, and clicks it. Cloud is what most buyers will run; an AGPL build exists if you want to self-host.
Founded in 2023 in San Francisco by Suchintan Singh, Kerem Yilmaz, and Shuchang Zheng. Y Combinator S23. $2.7 million seed, framed as money to stop the maintenance tax on vendor-portal invoice jobs and outdated government forms.
July 2026 is when the product left preview. Workflow Studio is out for all users. Human-in-the-loop approve/reject landed in the run view, and the public run API now reports paused. Self-heal is visible on the workflow list and the run page. Recurring add-on credits dropped to $0.90 per 1,000. Around 14–15 Jul they shipped Rustwright alpha, a Playwright-compatible runtime they say uses 70 percent less memory and boots 2.55× faster, without a Playwright driver fingerprint — not a claim it is undetectable.
Best for:
Ops and engineering teams automating credential-gated vendor portals and long forms, who want a workflow builder plus SDKs rather than a raw browser fleet.
Key Features:
- Vision navigation from the rendered UI, not CSS selectors.
- Native CAPTCHA and 2FA on Skyvern Cloud; 2FA / TOTP on Pro and above.
- Workflow Studio plus SDKs: a prompt, a saved workflow, or an API call.
- Planner / Actor / Validator loop — the validator checks whether the screen actually changed.
Why we like it:
Aimed at the job that burns calendar time: a vendor portal with a login, a date range, a download, and a UI that changes without notice. Most production failures are silent "I clicked, therefore it worked" errors. The validator is the right admission.
Notable Limitations:
- AGPL-3.0 is a different conversation than MIT if you embed the code in a closed product.
- Credits are the billing unit, and public pages do not say how many a real portal job burns. Budget from a metered pilot.
- Self-hosted Skyvern does not automatically include cloud CAPTCHA, 2FA, or identity extras.
- Rustwright is alpha. The 70 percent / 2.55× figures are their measurement, not a production SLA.
Pricing:
Plan stickers are unchanged. Free $0 with 5,000 credits. Hobby $29. Pro $149. Enterprise custom. Recurring add-on credits $0.90 per 1,000. Self-host via Docker if the license and the missing cloud extras are acceptable.
Browserbase
Managed browser infrastructure for teams that already have, or intend to write, their own agent logic. Hosted browsers, session replay, and identity / retrieval APIs. Stagehand is the open-source SDK on top: act, extract, observe, and agent.
Founded in 2024 in San Francisco by Paul Klein IV. Seed $7 million (June 2024, Kleiner Perkins), Series A $21 million (November 2024), Series B $40 million on 17 June 2025, led by Notable Capital. The PR said 1,000-plus companies; the homepage later showed 10,000 companies and 36,925,870 unique sessions in March 2026.
Stagehand, not a fifth product. Browserbase's SDK for mixing natural-language primitives with Playwright-level control. Around 10–11 Aug 2026 they shipped Stagehand v4: the core (target management, state, CDP dispatch) moves into a browser extension, with TypeScript, Python, and Go clients, and a new init — launch or connect, then Stagehand.create({ browser }). Their bench calls it about 2× faster than Playwright and about 80 percent more token-efficient. GitHub releases still showed 3.7.x on 18 Aug 2026; do not treat v4 as a 4.0.0 tag. Identity, CAPTCHA, Search, and Fetch still need a Browserbase session.
Best for:
Platform and agent teams that want someone else to run the browser fleet, and that will bring their own workflow logic or use Stagehand rather than a visual builder.
Key Features:
- Browser-as-a-service with concurrency tiers and hourly metering.
- Agent Identity and CAPTCHA handling on paid plans.
- Search and Fetch APIs so you are not keeping a full browser warm for every retrieval.
- Session replay: a failed run is a recording, not a null-selector log line.
Why we like it:
Most "we built an agent" projects die on browser operations: cold starts, IP reputation, session teardown, "it worked on my laptop." Browserbase is honest about being that layer. Stagehand is the right SDK if you want Playwright for the stable steps and an LLM only on the clicks that move.
Notable Limitations:
- No self-hosted browser fleet. The browsers are SaaS.
- Cost is a meter stack: hours, Search, Fetch, proxies. The sticker plan is not the bill.
- Free tier is one browser hour — enough to validate an SDK, not a production workflow.
- Local Stagehand is not the full product, and v4 is a blog-and-docs launch until a 4.0.0 tag shows up.
- Not a workflow product. If the buyer is an ops lead who wants a builder and a queue, Skyvern is the closer shape.
Pricing:
Unchanged. Free: 1 browser hour. Developer $20 / 100 hours, then $0.12/hour. Startup $99 / 500 hours, then $0.10/hour. Scale custom.
Anthropic Computer Use
A beta API tool that lets Claude operate a desktop the way a person does: screenshot, move a cursor, click, type, scroll, drag. It is not a hosted browser product. You implement the tool in your own sandbox and send the results back.
Public beta since October 2024. The header is still computer-use-2025-11-24 — schema version, not a claim it left beta. Docs now list claude-opus-5 and claude-sonnet-5; Opus 5 launched 24 Jul 2026. A Cowork / Claude Code computer-use research preview opened to Pro and Max on 1 Jul 2026. That is a consumer surface, not this API.
Best for:
Teams that already run Claude, need desktop or mixed GUI control rather than a browser-only fleet, and can bring their own VM or container.
Key Features:
- Screenshot, click, type, scroll, and drag against a live desktop — browser, spreadsheet, or native app.
- Zoom on the current schema, for small controls and calendar cells.
- Optional bash and text-editor tools in the same request.
- Prompt-injection classifiers on screenshots, with a forced confirmation when page content tries to override the operator.
Why we like it:
Honest about the execution surface: a desktop, not a cleaned-up DOM. If the workflow jumps from a PDF to a legacy portal to a spreadsheet, a browser-only agent is the wrong abstraction. It also publishes the token tax most "agent products" hide inside credits.
Notable Limitations:
- Still beta. You implement the tool. Anthropic does not run the desktop.
- Latency is a first-class limit. The docs tell you to pick tasks where speed is not critical.
- Vision errors are expected: missed coordinates, wrong controls, hallucinated success.
- Prompt injection is documented. Page content can override instructions even with classifiers on.
- No computer-use SKU. Every screenshot is a vision call on top of the system prompt and tool definition.
Pricing:
No separate SKU. Claude token rates, plus 466–499 system-prompt tokens for the beta, plus 735 tool-definition tokens on Claude 4.x, plus vision tokens every screenshot. Bring your own sandbox.
A later thread, Our Computer Using agent just solved CAPTCHA up to Level 6, is color only: “CAPTCHAs, browser popups, cookie banners, all the things that break every other agent? Ours just… handles them.” Broken Gates is still the measurement: commercial solvers near-perfect on challenge CAPTCHAs at about $0.10 per 1,000, and 23 percent on reCAPTCHA v3. Off-the-shelf LLM browser agents generally fail challenge CAPTCHAs unless a solver is wired in, and they fail v3 because a clean, instrumented browser looks like a bot. A June 2026 study found stealth modes can increase detectability rather than reduce it.
A June 2026 r/LocalLLaMA thread put the cloud-agent bill in one line:
Currently using cloud models for my browser use and it's great when it works but it's one of the last things keeping me subscribed.
Honorable mentions, and what we left out
Steel.dev belongs on an infrastructure shortlist next to Browserbase when the job is a hosted browser, not a workflow product.
Playwright MCP is the right mention when the workflow is stable enough that an agent loop is overhead. If the steps do not change, a deterministic Playwright path exposed through MCP will be cheaper and easier to debug. Use it when you can write the script, not as a substitute for vision-first portal work.
We are not covering general-purpose agent platforms — they orchestrate tools; they do not solve browser identity, session replay, or desktop GUI control — or OpenAI's sunset Operator / ChatGPT agent. A discontinued consumer agent is not a 2026 buying option.
Computer-Use & Browser Agent Tools Comparison: Quick Overview
| Tool | Best For | Pricing Model | Highlights |
|---|---|---|---|
| Browser Use | MIT library plus hosted browsers | Free 10 tasks / 3 concurrent; PAYG (min $5); Dev $29; Business $299; Scaleup $999; $0.02/browser-hour; residential $5/GB | OSS + SaaS; Harness / Agents API V4; /share/v4; 195-plus country proxies |
| Skyvern | Vision-first portal workflows | Free 5k credits; Hobby $29; Pro $149; Enterprise custom; add-on credits $0.90/1k | Planner / Actor / Validator; Studio GA; cloud CAPTCHA + 2FA; AGPL + Docker |
| Browserbase | Managed fleet; Stagehand SDK | Free 1 hour; Dev $20 / 100h then $0.12/h; Startup $99 / 500h then $0.10/h; Scale custom | Browser-as-a-service; Identity / CAPTCHA; Search + Fetch; replay; Stagehand v4 |
| Anthropic Computer Use | Desktop GUI via Claude | No CU SKU; Claude tokens + 466–499 system + 735 tool-def + vision / screenshot | Click / type / scroll / drag; zoom; bash + editor; classifiers; still beta |
Computer-Use & Browser Agent Platform Comparison: Key Features at a Glance
| Tool | Navigation style | Hosted identity extras | Workflow product | Open source |
|---|---|---|---|---|
| Browser Use | Agent loop over DOM and vision | Stealth, CAPTCHA, proxies on cloud | API-first agents, not a visual builder | Yes, MIT Python library |
| Skyvern | Vision-first Planner / Actor / Validator | Native CAPTCHA + 2FA on cloud / Pro+ | Yes, Studio + SDKs | Yes, AGPL-3.0 |
| Browserbase | BYO agent, or Stagehand act / extract / observe / agent | Agent Identity and CAPTCHA on paid plans | No; infrastructure plus SDK | Stagehand SDK; browsers are SaaS |
| Anthropic Computer Use | Screenshot-grounded desktop actions | None; you own the environment | No; you write the agent loop | Reference impl; beta API |
Computer-Use & Browser Agent Deployment Options
| Tool | Cloud | Self-host | Integration complexity |
|---|---|---|---|
| Browser Use | Hosted agents and browsers | Yes, OSS library on your browsers | Low–moderate for the library; higher once proxies matter |
| Skyvern | Yes | Yes, Docker, without cloud extras | Moderate; workflow setup is the work |
| Browserbase | Browsers are SaaS | Stagehand locally; no self-hosted fleet | Low if you speak Playwright; higher with identity + meters |
| Anthropic Computer Use | API only | You bring the sandbox, VM, or container | High; you implement the tool and the loop |
Computer-Use & Browser Agent Strategic Decision Framework
| Critical Question | Why It Matters | What to Evaluate | Red Flags |
|---|---|---|---|
| Workflow, fleet, or desktop? | Wrong shape means a second vendor in six months. | Ops builder (Skyvern), engineering fleet (Browserbase), GUI that leaves the browser (Anthropic). | A general agent platform that "also does browsers." |
| How long is the real task? | Long-horizon completion collapses as the job stretches. | Step budget, checkpointing, replay, and whether the agent stops researching and submits. | A short live-web score sold as proof a 90-minute job will finish. |
| Challenge CAPTCHA or risk score? | Puzzles and environment checks fail for different reasons. | Whether extras live only on the vendor cloud, and whether the runtime looks long-lived. | A pitch that "stealth" makes the agent look human. |
| License and data path? | MIT, AGPL, and a closed beta API are different constraints. | AGPL on Skyvern OSS, MIT on Browser Use, Stagehand OSS, no self-host fleet on Browserbase, BYO sandbox on Anthropic. | "Open source" used as a synonym for the hosted product. |
| How do you meter a failed run? | Credits, hours, proxy GB, and vision tokens all bill retries. | A published rate card, a step cap, and a replay that does not re-call the model. | Credit opacity, or a free tier too small to measure the job (1 hour; 10 tasks). |
| Who implements the last mile? | Anthropic does not run a desktop. Browserbase does not ship your workflow. | Time for the sandbox, the tool handler, and verification. | A quote that prices only tokens or only hours. |
Computer-Use & Browser Agent Solutions Comparison: Pricing & Capabilities Overview
| Organization size | Recommended setup | Monthly cost | Annual investment |
|---|---|---|---|
| Startup, pre-scale | Browser Use Free/Dev or Skyvern Free/Hobby for one portal; Browserbase Free only to validate Stagehand | Browser Use $0 or $29; Skyvern $0 or $29; Browserbase Free (1h) or $20 | $0 to a few hundred on published tiers; confirm overage (hours, credits, $5/GB residential) |
| Mid-market, regional | One workflow product or one fleet, not both, until a pilot shows which layer fails | Skyvern Pro $149; Browser Use Business $299; Browserbase Startup $99 then $0.10/hour | Published tiers plus usage. Do not annualize credits without a production trace. |
| Enterprise, mixed desktop and web | Skyvern or Browser Use cloud for portals; Browserbase if you own the agent; Anthropic only if you staff the sandbox | Browser Use Scaleup $999 or custom; Skyvern Enterprise custom; Browserbase Scale custom; Anthropic token-metered | Custom tiers not public. Anthropic: Claude tokens + 466–499 system + 735 tool-def + vision / screenshot. |
Only the published numbers above are usable in a budget. Confirm current rates before a purchase order.
Bottom Line on AI Computer-Use and Browser Agents
Match the product to the job. Vendor portal with a login and a download: Skyvern or Browser Use, measured on the same three portals. "We have an agent, we need browsers that stay up": Browserbase and Stagehand. The work leaves the browser: Anthropic Computer Use, and you are signing up to build the sandbox.
Keep two columns. Do not average them. Column A is the independent long-horizon table in the intro. Column B is vendor WebVoyager: Skyvern's own post puts Browser Use at 89.1 percent and Skyvern 2.0 at 85.85 percent. Those scores are self-reported and demo-shaped — short live-web tasks on a small site set, not a production rate for a 90-minute internal workflow. One vendor-claim note is enough: treat marketing benches as directional, then read the trace on your own portal.
Environment authenticity is a product feature, not a prompt. A solver story for puzzle CAPTCHAs will not fix a risk score that rejects a clean automation browser. Pilot on the real portal, with the real login, and read the trace at step 500.
