Browser Use: 10 AI browsers in parallel with Claude Code or Codex, even on sites with anti-bot and CAPTCHAs

With Browser Use you can open dozens of browsers at the same time and have each one driven by a Claude Code or Codex subagent. Every agent browses, clicks, fills in forms and reads pages the way a person would. Browser Use is an open-source project with a Cloud version too: according to the company’s own benchmark, Cloud browsers get past anti-bot protection in 81% of cases across 71 high-security sites.

What is Browser Use?

Browser Use is an open-source Python library, MIT-licensed, that lets an AI agent control a real browser. The agent gets a task in plain language and carries it out on the page: it opens the URL, finds the button, fills in the form, reads the result.

The interesting part comes when Browser Use is combined with Claude Code or Codex subagents. Each subagent takes one browser and a different task. So instead of one agent working on one site at a time, you have ten working in parallel.

What can you do with 10 browsers in parallel?

I see three concrete uses:

• Build a management tool that works on other portals by itself: the agent logs in, enters or downloads data, and comes back with the result.
• Test your web app: 10 features checked at once, for example login, sign-up and checkout, each in its own browser.
• Automate repetitive tasks for your clients: the procedures on external portals that someone still does by hand every week.

When an automation like this has to become a stable part of a company’s processes, the work moves beyond a single script and becomes a custom software development project: it needs maintenance, monitoring and a connection to internal data.

How do you use Browser Use Cloud with Claude Code or Codex?

The first option is Browser Use Cloud. You pay for a service that gives you ready-made browsers with stealth systems, residential proxies and automatic CAPTCHA solving.

The Cloud browsers connect to Claude Code or Codex, and you drive them with the models included in your subscription. You don’t need a separate API for the model. You only pay Browser Use for browser time and traffic: on the pricing page, checked on October 16, 2026, that is $0.02 per hour per session and $5 per GB of proxy traffic.

So you can start several browsers together, assign each one to a subagent and give every subagent a different task.

How well does it really work against anti-bot systems and CAPTCHAs?

My starting point is Browser Use’s own figure. In the benchmark published on March 21, 2026, Browser Use Cloud avoided being blocked in 81% of cases across 71 sites protected by anti-bot systems. In the same test Anchor reached 77% and Kernel 67%.

Two details matter when reading that number:

• the benchmark was run by the company itself: there is no independent measurement yet;
• the test only measures whether the agent gets blocked by anti-bot protection, and leaves task completion out.

The number is still a good signal: on sites designed to stop bots, the Cloud version gets through more than four times out of five.

There is also a limit I ran into when I tried it. Claude Code often refuses to get past CAPTCHAs unless it is 100% sure of one of these three conditions:

• you are in a test environment;
• you are authorized to do it;
• the site is yours.

Keep this in mind before you hand Claude Code a third-party portal protected by CAPTCHAs.

How do you install Browser Use for free on your own PC or VPS?

The second option is free. Browser Use is open source, so you install the software on your PC or on a VPS, a Virtual Private Server. You need Python 3.11 or later.

To run 10 browsers in parallel you can use Python with asyncio, the standard library for running several operations at the same time. Claude Code knows it very well, so you can ask it to write all the code.

In the open-source version you handle anti-bot systems and CAPTCHAs yourself, with external tools:

• Proxies: they reduce blocks tied to your IP address.
• Rebrowser: a set of patches for Puppeteer and Playwright that reduces the traces that give away an automated browser.
• NopeCHA: an automatic CAPTCHA-solving service.

These tools are separate from Browser Use. You have to configure them, check their compatibility, and some of them cost money. Here too you can let Claude Code do the setup work.

Which version should you pick?

The choice depends on how much time you want to spend on infrastructure. Browser Use Cloud gives you ready browsers, with proxies and CAPTCHAs already handled, and you pay as you go. The open-source version is free, but proxies, stealth and CAPTCHAs become your job to configure and maintain.

If you want to try an idea quickly, start with Cloud. If the automation runs every day on your VPS and you want full control, the open-source version makes sense. For orchestrating several agents in parallel on the same project, I also wrote about how Spotify does it with tmux and git worktree.

Pick the first repetitive task you do every week on an external portal: it is the right candidate for your first test with ten browsers in parallel.