BROWSER USE

- Browser Use Agents: give Browser Use a task and receive completed work. API V4 is current for new integrations.
- Browser Infrastructure: connect your agent or automation to managed browsers through SDK, REST, or CDP. Starts at $0.02/browser-hour.
- Developer tools: Open Source, Browser Harness, SDK, and MCP support the two products above.

[Developer Index](https://browser-use.com/index.md)
[Product Map](https://browser-use.com/llms.txt)
[Full Product Context](https://browser-use.com/llms-full.txt)
[Pricing](https://browser-use.com/pricing.md)
[Cloud Docs](https://docs.browser-use.com/cloud/quickstart)
[Open Source Docs](https://docs.browser-use.com/open-source/introduction)

---

# agent-browser vs Browser Harness

Comparison | [Browser Harness](https://browser-use.com/browser-harness)

## agent-browser vs Browser Harness.

Both are browser CLIs for coding agents. On 100 public browser tasks Browser Harness used 64% of the median input tokens and finished faster, and it starts in your real Chrome.

[Try it in the cloud](https://cloud.browser-use.com/v4?utm_source=browser-use&utm_medium=agent-browser-page)

Connect your agent

[Open my X profile, find my latest 20 video posts, and download them.](https://browser-use.com/showcase/videos/download-latest-20-x-videos.mp4)

PromptOpen my X profile, find my latest 20 video posts, and download them.

## Side by side

Browser Harness agent-browser

Score on 100 browser tasks: Browser Harness: 60.4 / 100; agent-browser: 56.3 / 100, a statistical tie

Input tokens per task (median): Browser Harness: 2.1M; agent-browser: 3.3M

Agent cost per task (median): Browser Harness: $0.042; agent-browser: $0.056

Agent time per task (median): Browser Harness: 9.0 min; agent-browser: 11.3 min

Browser: Browser Harness: Your Chrome, with your logins; agent-browser: Headless Chrome by default. Your Chrome via --auto-connect or --profile

Setup: Browser Harness: Paste one prompt into your agent; agent-browser: npm install -g agent-browser, then agent-browser install

Missing tool: Browser Harness: The agent writes it and keeps it; agent-browser: Large built-in command set, extended by plugins

Cloud browsers: Browser Harness: Browser Use cloud, $0.02 per browser-hour; agent-browser: Providers include Browserbase, Browserless, Browser Use and Kernel

License: Browser Harness: MIT; agent-browser: Apache-2.0

Pick agent-browser for a fast headless CLI with a fixed, documented command set.

Source: [Matched eval: method and per-task scores](https://browser-use.com/benchmarks/coding-agent-browser-tools.json), [BU Bench V2.1 tasks](https://github.com/browser-use/benchmark), [agent-browser README](https://github.com/vercel-labs/agent-browser), checked Oct 2026.

## Questions

Is Browser Harness better than agent-browser?

On success, neither wins. On 100 public BU Bench V2.1 tasks with the same agent (Codex, GPT-6 Luna), the same cloud browser and the same judge, Browser Harness scored 60.4 and agent-browser 56.3 out of 100; the paired difference has a 95% interval of -1.8 to +10.0 points, which includes zero. The difference is cost: agent-browser used 1.6x the input tokens per task (median 3.3M vs 2.1M), so the agent's bill was $0.056 vs $0.042 per task. One run per task; per-task scores are public.

Can agent-browser use Browser Use cloud browsers?

Yes. Browser Use is one of its cloud providers, so you get the same cloud browsers either way.

Which agents does Browser Harness work with?

Claude Code, Codex, Cursor, Gemini CLI, Hermes Agent and OpenClaw. Anything that can run a shell command.

What does it cost?

Nothing. Browser Harness is open source under MIT, and using your own Chrome is free. Cloud browsers are $0.02 per browser-hour if you want them.

You will never use  
the browser again.

[Try it in the cloud](https://cloud.browser-use.com/v4?utm_source=browser-use&utm_medium=agent-browser-page)

Connect your agent