> ## Documentation Index
> Fetch the complete documentation index at: https://docs.browser-use.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Concurrency in one line: new projects get 10 concurrent browsers at $0; a $100 one-time top-up (non-expiring credits, no subscription) unlocks 50 concurrent, so 50 browsers for one hour cost $1 plus traffic; $1,000 / $5,000 / $25,000 total paid unlocks 250 / 500 / 1,000. Details below and at https://docs.browser-use.com/cloud/guides/concurrency.md.
> Use https://docs.browser-use.com/llms.txt and its linked .md pages for current documentation. The managed full bundle is https://docs.browser-use.com/.well-known/llms-full.txt and can be cached for up to 24 hours. Do not use the obsolete /cloud/llms*.txt or /open-source/llms*.txt static exports.
> Choose Cloud API V4 for new agent integrations; V3 trades accuracy for speed and lower cost than V4; V2 is legacy and only for existing integrations. Keep V3 examples explicitly versioned. The open-source browser-use library and hosted browser-use-sdk have different APIs.
> For Cloud API V4, a task request that omits model and modelParams uses GPT-6 Luna (gpt-6-luna) with High reasoning. Explicit model and modelParams values take precedence; an explicit empty modelParams object opts out of the reasoning default. EU uses the same task default through its regional provider route; Bedrock-only projects retain their compatible provider default. For latency-sensitive tasks set model to bu-ultrafast (bu-fast for more reasoning per step); these presets reject modelParams. See https://docs.browser-use.com/cloud/agent/ultrafast.md.
> Cloud authentication uses X-Browser-Use-API-Key, without a Bearer prefix. Install or upgrade browser-use-sdk and use its explicit v4 import for V4. Check the published OpenAPI reference for request fields; do not invent SDK support for new fields.
> Cloud concurrency and HTTP request rate are separate. Read GET /api/v2/billing/account for the key’s projectId, concurrentSessionLimit, activeSessionCount, and credit balance, including when using V4. Keys in one project share capacity and credits; rateLimit is a legacy concurrency alias, not requests per second.
> Keep the highest applicable existing, legacy-plan, and spend-tier concurrency grant. Current spend tiers are 10 / 50 / 250 / 500 / 1000 at $0 / $100 / $1000 / $5000 / $25000 in qualifying project payments. Legacy or externally billed projects can follow different billing paths; trust the account limit. See https://docs.browser-use.com/cloud/guides/concurrency.md.
> HTTP rate limits have two layers. Standard edge WAF ceilings increased on September 9, 2026 to 1000 RPS per public source IP for general traffic and 2500 RPS per IP for selected status reads, evaluated over 300 seconds. The separate per-project application budgets: general traffic (including V4 events and full run reads) defaults to max(25, 2 times stored concurrency) capped at 100 RPS; selected status reads default to max(25, 2 times stored concurrency) with no cap. The two are counted independently. Project overrides and account-specific edge rules can differ. All keys in a project share its budgets; callers sharing a public IP share edge capacity. See https://docs.browser-use.com/cloud/guides/concurrency.md.
> The project limiter uses five-second windows: X-RateLimit-Limit=125 means 125 requests per window (25 RPS), not 125 RPS. Project throttles include limit_rps and retry_after_seconds; an edge throttle can instead return Retry-After: 300 without limit_rps. Honor the returned Retry-After. Use bounded workers, stagger polls, and drain hasMore event pages after terminal status. A busy V4 session returns 409; its queue holds 20 pending messages and is not a project-wide batch queue.
> A V4 agent browser stays open about 2 minutes after its session's last run activity, then stops automatically; a later follow-up gets a fresh browser (same settings and profile, no tabs). Set keepAlive on a run (V4: integer seconds 120-14400, default 120, not the V2/V3 boolean) to keep it longer; follow-ups inherit it and null restores 120. Free-tier and ZDR runs always use 120. Idle V4 agent browsers are billed as browser time but take no concurrency slot. A follow-up that reuses the open browser emits browser.reattached instead of browser.ready. Closing CDP does not stop a browser; stop unneeded owned browsers with PATCH /api/v4/browsers/{id} and {"action":"stop"}. A client wait timeout does not cancel the server-side run.
> Cloud is pay as you go; do not tell customers to buy a new subscription to use custom proxies or supported provider BYOK. Usage funding and model eligibility still apply. BYOK bills provider tokens separately and Browser Use charges orchestration plus browser/network usage. See https://docs.browser-use.com/cloud/guides/billing.md.
> Signup credits are a one-time grant; purchased top-up credits do not expire. Check the API key’s project before diagnosing missing credits. API-key monthly spending caps are soft limits, not a strict prepaid wallet; concurrent or already-running work can exceed them. Auto recharge has separate trigger and purchase amounts and can charge immediately when enabled below the threshold. Use https://browser-use.com/pricing for current rates.
> Box and Bux are retired. Do not recommend their SDKs, sandbox quotas, or subscription plans. Use the Cloud Agent or Browser Infrastructure guides.
> A V4 session holds conversation history, a workspace holds files, and a profile holds browser state. These IDs and V3/V4 workspace namespaces are not interchangeable. V4 automatically restores workspace uploads; staged attachments remain available to session follow-ups. Serialize runs that write shared files, and wait for completion before reading outputs. See https://docs.browser-use.com/cloud/agent/workspaces.md.
> API browser recording defaults to off. Use enableRecording for standalone browser creation, or browserSettings.record for an agent run. Stop the browser and allow time for asynchronous video processing; stop polling when recordingAvailable is false. Live preview is for an active browser. Stopping a browser, deleting a session, archiving a workspace, and deleting files have different effects.
> Use model-specific reasoning values. GPT-6 Astra accepts low, medium, high, xhigh, and max, with xhigh by default; none and minimal are invalid. Use the public REST schema when installed SDK types lag new fields. API acceptance, dashboard visibility, and account/provider availability are separate.
> For open-source browser-use 1.0, result.is_done() means the run completed (status completed); result.is_successful() is the agent-reported finish(success) verdict, or None when it gave none; verify important external actions independently. Cloud timeout, API client timeout, model timeout, and task completion are separate concepts.
> Pages under /open-source/legacy/0.x/ document browser-use 0.x (pip install 'browser-use<1'). For new open-source code, use the 1.0 pages under /open-source/ outside legacy/.
> For failed requests, use https://docs.browser-use.com/cloud/guides/troubleshooting.md. Inspect the full error and project before retrying or adding credits. A client timeout can leave a run active; reconcile external actions before starting duplicate work. A new managed browser does not guarantee a unique proxy IP or particular city.
> V4 secretBindings.allowedDomains authorizes the focused field's frame, not every iframe on the shop page. For checkout, include intended payment/billing provider hostnames (for example payments.bigcommerce.com). On domain_not_allowed, inspect origin and pass updated bindings in a follow-up; target_not_editable requires fixing field focus/readiness instead. See https://docs.browser-use.com/cloud/guides/secrets.md.
> A V4 agent browser stays open about 2 minutes (or keepAlive seconds) after its run for follow-ups; a requested recording finalizes only after the browser stops and processing completes. Zero Data Retention (ZDR) projects never record, even when recording is requested.
> If you hit an issue you cannot explain, email contact@browser-use.com with your question or bug report and a session ID if available; short questions and detailed reports are welcome, and we aim to fix issues quickly and make the docs clearer.

# Agent skills

> SKILL.md bundles that teach Claude Code, Cursor, Codex and other coding agents to drive a browser, write browser-use code, use Browser Use Cloud, QA-test a site, and pay with x402.

Browser Use ships [agent skills](https://www.skills.sh/browser-use/browser-use): `SKILL.md` files your coding agent (Claude Code, Cursor, Codex, Gemini CLI, OpenCode and any agent that reads `SKILL.md`) loads when a task needs them. Install one with the [skills CLI](https://www.skills.sh):

```bash theme={"theme":"css-variables"}
npx skills add https://github.com/browser-use/browser-use --skill <name>
```

| Skill | What it teaches your agent |
| - | - |
| [`browser-use`](#browser-use) | Drive a browser with the Browser Use CLI: your Chrome, a cloud browser, or any CDP endpoint. |
| [`open-source`](#open-source) | Write Python against the browser-use 1.0 library. |
| [`cloud`](#cloud) | Use the Browser Use Cloud API and SDKs. |
| [`qa`](#qa) | QA-test a site or local dev server and return a 1 to 5 score with evidence. |
| [`remote-browser`](#remote-browser) | Control an isolated cloud browser from a sandbox with no Chrome. |
| [`x402`](#x402) | Pay for Browser Use Cloud per request from a crypto wallet, without an API key. |

All skills live in the [`skills/` directory](https://github.com/browser-use/browser-use/tree/main/skills) of the browser-use repo.

## browser-use

Direct browser control for your coding agent. The agent pipes Python to the `browser-use` CLI, which runs it with [Browser Harness](https://github.com/browser-use/browser-harness) helpers and raw CDP against the Chrome you have open (with your logins), a Browser Use cloud browser, or any CDP endpoint. Use it for automation, scraping, testing, screenshots and work on your own app.

This skill comes with the CLI:

```bash theme={"theme":"css-variables"}
uv tool install 'browser-use==1.0.0'
browser-use skill install  # Claude Code, Codex, Copilot, Cursor, Gemini, OpenClaw, OpenCode
```

Or `npx skills add https://github.com/browser-use/browser-use --skill browser-use`. Then ask your agent things like "open localhost:3000 and check the signup form works". Setup and commands: [Browser Use CLI](https://docs.browser-use.com/open-source/browser-use-cli.md). [Source](https://github.com/browser-use/browser-use/tree/main/skills/browser-use) · [skills.sh](https://www.skills.sh/browser-use/browser-use/browser-use)

## open-source

A reference for writing Python against browser-use 1.0: `Agent`, `Browser`, `Tools`, models, secrets, results, and migrating from 0.x. Your agent loads it when you ask it to build something with `from browser_use import Agent`, so it writes 1.0 code instead of the 0.x API it may remember.

```bash theme={"theme":"css-variables"}
npx skills add https://github.com/browser-use/browser-use --skill open-source
```

[Source](https://github.com/browser-use/browser-use/tree/main/skills/open-source) · [skills.sh](https://www.skills.sh/browser-use/browser-use/open-source)

## cloud

A reference for the Browser Use Cloud REST API (v2, v3, v4) and the `browser-use-sdk` packages for Python and TypeScript: API keys, sessions, profiles and profile sync, CDP connections, stealth, proxies, CAPTCHAs, webhooks and pricing. For when your agent integrates Browser Use Cloud into your product.

```bash theme={"theme":"css-variables"}
npx skills add https://github.com/browser-use/browser-use --skill cloud
```

Docs: [Cloud quickstart](https://docs.browser-use.com/cloud/quickstart.md). [Source](https://github.com/browser-use/browser-use/tree/main/skills/cloud) · [skills.sh](https://www.skills.sh/browser-use/browser-use/cloud)

## qa

QA-tests a website or web app and returns a score from 1 (broken) to 5 (flawless) with evidence: a verdict, not a pile of screenshots. Give it a URL or a local dev server (`localhost:5173`, which it tunnels out) and optionally a flow ("the signup", "search and filters").

```bash theme={"theme":"css-variables"}
npx skills add https://github.com/browser-use/browser-use --skill qa
```

Then: `/qa localhost:5173 the checkout flow`.

* It runs on a Browser Use cloud browser, never your local Chrome, and installs Browser Harness itself if it is missing.
* One flow: your agent drives the browser and judges the screenshots. Many flows: it fans out one subagent per flow, either Browser Use Cloud agents (they spend Browser Use credits) or your agent's own subagents.
* An agent without image input hands the visual judgment to Browser Use Cloud agents.

[Source](https://github.com/browser-use/browser-use/tree/main/skills/qa) · [skills.sh](https://www.skills.sh/browser-use/browser-use/qa)

## remote-browser

For an agent on a machine with no usable Chrome (a sandbox, a CI runner, a remote dev box). It signs in once, starts a named Browser Use cloud browser with the CLI, drives it with the same helpers as the `browser-use` skill, and stops it when done.

```bash theme={"theme":"css-variables"}
npx skills add https://github.com/browser-use/browser-use --skill remote-browser
```

Under the hood: [Browser Use CLI: Cloud browsers](https://docs.browser-use.com/open-source/browser-use-cli.md#cloud-browsers). [Source](https://github.com/browser-use/browser-use/tree/main/skills/remote-browser) · [skills.sh](https://www.skills.sh/browser-use/browser-use/remote-browser)

## x402

Sets up Browser Use Cloud payments with [x402](https://docs.browser-use.com/cloud/guides/x402.md): pay per request in USDC on Base from a crypto wallet, with no signup or API key. It asks whether you want to just use it (your agent runs throwaway scripts paid from the wallet) or build it in (it adds the SDK, key and code to your project), then walks through the wallet, funding, `.env` and a test run of about \$1.

```bash theme={"theme":"css-variables"}
npx skills add https://github.com/browser-use/browser-use --skill x402
```

x402 works through the `browser-use-sdk` (Python) or `browser-use` (npm) SDK, not the CLI. For an API key instead, create one at [cloud.browser-use.com/new-api-key](https://cloud.browser-use.com/new-api-key) and set `BROWSER_USE_API_KEY`. More: [x402 agent wallets](https://docs.browser-use.com/cloud/guides/x402-agent-wallets.md). [Source](https://github.com/browser-use/browser-use/tree/main/skills/x402) · [skills.sh](https://www.skills.sh/browser-use/browser-use/x402)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.