cloud skill
Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2, v3, or v4), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP WebSocket connections, stealth browsers, residential proxies, CAPTCHA handling, webhooks, workspaces, skills marketplace, liveUrl streaming, pricing, or integration patterns (chat UI, subagent, adding browser tools to existing agents). Also trigger for questions about n8n/Make/Zapier integration, Playwright/ Puppeteer/Selenium on cloud infrastructure, or 1Password vault integration. Do NOT use this for the open-source Python library (Agent, Browser, Tools config) — use the open-source skill instead.
Is the cloud skill safe?
Serious findings: read the flagged lines first. We read 12 files in the folder on 2026-11-14.
- high
references/quickstart.md:164Downloads a script and runs it in one step, so what runs is whatever that server sends that day. Common for installers, and still worth a look at the address.
- Profile sync (easiest): `curl -fsSL https://browser-use.com/profile.sh | sh` - high
references/sessions.md:92Downloads a script and runs it in one step, so what runs is whatever that server sends that day. Common for installers, and still worth a look at the address.
curl -fsSL https://browser-use.com/profile.sh | sh
Install the cloud skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. Read the findings above first.
git clone --depth 1 https://github.com/browser-use/browser-use.git /tmp/browser-use mkdir -p ~/.claude/skills cp -r /tmp/browser-use/skills/cloud ~/.claude/skills/cloud
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
Browser Use Cloud Reference
Reference docs for the Cloud REST API, SDKs, and integration patterns. Read the relevant file based on what the user needs.
Choose a starter
- Hosted task in, result out: use the V4 SDK runs resource in references/api-v4.md.
- Your existing agent needs a browser: use the V4 SDK browsers resource or REST/CDP, then explicitly stop the browser.
- Local framework development: use the open-source browser-use skill, not Cloud SDK calls.
Eligible new Google, GitHub or Microsoft signups get a one-time $1 Cloud credit. No card required; email/password signups do not qualify. Pricing and eligibility. Use gpt-5.6-luna for the free starter; paid-only models need a top-up.
Reuse BROWSERUSEAPI_KEY, or guide the user through Cloud signup and key creation. Keep keys server-side, never in prompts or client bundles.
API & Platform
Integration Guides
Critical Notes
- Use v4 for new hosted-agent integrations. Keep v2 or v3 only when maintaining an existing integration or using a resource not yet wrapped by the v4 SDK.
- Cloud API base URL: https://api.browser-use.com/api/v2/ (v2), https://api.browser-use.com/api/v3 (v3), or https://api.browser-use.com/api/v4 (v4)
- Auth header: X-Browser-Use-API-Key:
- Get API key: https://cloud.browser-use.com/new-api-key
- Set env var: BROWSERUSEAPI_KEY=
- Cloud SDK: uv pip install browser-use-sdk (Python) or npm install browser-use-sdk (TypeScript)
- Python v2: from browserusesdk import AsyncBrowserUse
- Python v3: from browserusesdk.v3 import AsyncBrowserUse
- Python v4: from browserusesdk.v4 import BrowserUse or AsyncBrowserUse
- TypeScript v2: import { BrowserUse } from "browser-use-sdk"
- TypeScript v3: import { BrowserUse } from "browser-use-sdk/v3"
- TypeScript v4: import { BrowserUse } from "browser-use-sdk/v4"
More skills from browser-use/browser-use
- Abrowser-useDirect browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser()), Playwright, Puppeteer or any CDP client.
- Abrowser-useDirect browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser()), Playwright, Puppeteer or any CDP client.
- Aopen-sourceReference for writing Python code against the browser-use 1.0 open-source library (Agent, Browser, Tools, models, sensitive data, results). Use it whenever the user writes code that imports from browser_use, asks about Agent or Browser options, supported models, custom tools, or migrating from browser-use 0.x. Do NOT use this for Cloud API/SDK usage or pricing (use the cloud skill), or for driving a browser through the CLI (use the browser-use skill).
- CqaQA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence. Use when the user wants to test, QA, evaluate, score, or "check how good" a site, page, flow, or app — including a local dev server (e.g. "qa test localhost:5173", "does the checkout work?", "rate this landing page"). Drives a real Browser Use cloud browser, tunneling localhost automatically.
- Aremote-browserControls an isolated Browser Use Cloud browser from a sandboxed machine with the current Browser Use CLI.
- Ax402Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For an API key instead, run `browser-use login` or use the `cloud` skill.