browser-use
browser-use is an open-source Python library that makes websites accessible to AI agents. It lets an agent drive a real browser the way a human does, opening pages, clicking buttons, typing, and filling in forms, so a task described in natural language can be completed end to end. Rechecked 2026-08-21: the first-party repo is github.com/browser-use/browser-use, MIT licensed, with 109,924 stars and 3,454+ forks, created 2024-10-31. It is one of the most-starred AI agent infrastructure projects.
Built on Playwright, browser-use connects a large language model to a live Chromium browser. It is used both as a standalone automation layer and as a skill for agent CLIs such as Claude Code, Codex, Cursor, Hermes, and OpenClaw.
Key Features
- Human-like browsing: the agent opens pages, clicks, types, and fills forms just like a person.
- Natural-language tasks: describe what to do, such as "fill in this job application" or "extract my followers to a CSV," and it completes the task.
- Form filling and data extraction: structured data can be scraped and exported, for example to CSV.
- Skill integration: install the
browser-useskill so agent CLIs (Claude Code, Codex, Cursor, Hermes, OpenClaw) can set it up automatically. - Cloud option: Browser Use Cloud handles hosting and scaling when you do not want to run it yourself.
Use Cases
- AI agents that need to interact with real websites for automation and testing.
- Scraping and extraction: pull structured data from pages and export it.
- Workflow automation: agents that fill forms, apply to jobs, or manage accounts online.
Pricing
| Plan | Price | Details |
|---|---|---|
| Open source | $0 | Self-hosted Python library, MIT licensed |
| Browser Use Cloud | Varies | Managed hosting and scaling; see browser-use.com |
The core library is free and open source; the Cloud product is priced separately on browser-use.com.
Advantages
- Huge adoption: 109k+ stars make it a de facto standard for browser automation in agent stacks.
- Real browser: drives actual Chromium rather than a fake DOM, so results reflect what a user sees.
- Agent-ready: works as a skill inside popular coding-agent CLIs.
Getting Started
- Install with
uvon Python 3.12 (recommended), orpip install browser-use. - Connect the library to your browser.
- Give an agent a task, or use it directly in Python to automate a page.
- For agent CLIs, run
browser-use skill installto register the skill.
See github.com/browser-use/browser-use and the docs.
Frequently Asked Questions
Is browser-use free?
The core library is open source under MIT. Browser Use Cloud is a separate paid product.
What browsers does it support?
It is built on Playwright, so it drives Chromium and other Playwright-supported browsers.
Can I use it inside Claude Code or Codex?
Yes. It ships as a skill that agent CLIs such as Claude Code, Codex, Cursor, Hermes, and OpenClaw can install.
Alternatives
- Playwright: the underlying multi-browser automation library.
- Chrome DevTools MCP: Google's MCP server that gives agents a live Chrome.
- Kitesurf: Cloudflare's hosted browser for agents.
Tips
- Prefer
uvwith Python 3.12 for a clean install. - Use the skill installer inside your agent CLI to avoid manual setup.
- For production workloads, evaluate Browser Use Cloud instead of self-hosting.
Conclusion
If you are building agents that need to actually use the web, browser-use is the de facto open-source layer to start with. Begin at github.com/browser-use/browser-use.
Comments
No comments yet. Be the first to comment!
Related Tools
Steel
steel.dev
Open-source browser API for agents. Cloud Launch is $0 plus usage with a one-time $30 credit. Scale is $250/month plus usage.
Kitesurf
kitesurf.cloudflare.app
Cloudflare agent browser on Workers. Rechecked: free in Browser Run beta. GitHub 404. Not an open-source Chromium clone.
Browserbase
www.browserbase.com
Hosted browser infra for agents. Developer is $20/month. Startup is $99/month. Scale starts at $249/month after a custom form.
Related Insights
Hook OpenCode Go into Codex on Windows. Do Not Open a Second Toolkit.
A ChatGPT-signed Codex desktop app still shows mostly GPT in the picker. On Windows, enable only OpenCode Go and the Grok, GLM, Kimi, DeepSeek, and MiniMax models you already pay for appear in the same selector. Keys stay local. Native GPT stays put.
What Locks Codex Is the Picker, Not the Models
You already pay for OpenCode Go, Grok, and Z.ai, but the Codex picker still shows mostly GPT. The community project codex-router does not teach another install ritual. It puts subscriptions you already bought back into the selector, keeps keys on the machine, and leaves native GPT alone.
Seven AI Coding CLIs, Six Months: No Matter How Strong the Model, Work Needs Supervision
Claude Code, Codex, opencode, pi, omp and DeepSeek Harness all have personalities. After six months of deep use I run a division of labor: pi for the fastest cheapest reviews, omp for complex PRs, DeepSeek Harness on V4 Flash for high-frequency low-cost review, and Claude Code, Qoder and Cursor for writing. No matter how strong the model, work needs supervision — ideally from an independent third party.