cloud — Claude Code skill: what it does, how to install
This skill covers Browser Use Cloud, its API, and SDKs for browser automation. Use it when building a hosted integration or maintaining v2 or v3.
npx skills add browser-use/browser-use --skill cloud -a claude-codeWhat cloud does
The skill covers Cloud REST API versions v2, v3, and v4, the browser-use-sdk for Python and TypeScript, X-Browser-Use-API-Key authentication, and cloud sessions. Its references include browser profiles, profile sync, CDP WebSocket, stealth browsers, residential proxies, CAPTCHA handling, webhooks, and live view.
It also documents workspaces, the skills marketplace, MCP, 1Password, Playwright, Puppeteer, Selenium, and integrations with n8n, Make, and Zapier. v4 is the recommended route for new hosted-agent integrations; v2 and v3 remain relevant for existing integrations and resources not yet wrapped by the v4 SDK.
You need an API key and should keep it server-side rather than in prompts or client bundles. CDP has a billing detail worth checking: closing the connection does not stop the browser, so the browser must be stopped explicitly.
What it helps with
- choose the right Cloud REST API version
- connect
browser-use-sdkfrom Python or TypeScript - configure cloud sessions and browser profiles
- add CDP access for Playwright, Puppeteer, or Selenium
- plan an n8n, Make, or Zapier integration
Example prompts for the agent
- Explain how to start a new hosted-agent integration with the v4 SDK and `BROWSER_USE_API_KEY`.
- Show how to connect an existing agent through CDP and stop the browser correctly.
- Walk me through browser profiles, webhooks, and live view for a cloud session.
How to install cloud
1Skills CLI (Vercel)
npx skills add browser-use/browser-use --skill cloud -a claude-code2Manually: put the files in place
~/.claude/skills/cloud/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cloud/
1Skills CLI (Vercel)
npx skills add browser-use/browser-use --skill cloud -a codex2Manually: put the files in place
.agents/skills/cloud/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add browser-use/browser-use --skill cloud -a cursor2Manually: put the files in place
.cursor/skills/cloud/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install browser-use/browser-use cloud2Manually: put the files in place
.github/skills/cloud/SKILL.md1Skills CLI (Vercel)
npx skills add browser-use/browser-use --skill cloud -a gemini-cli2Platform CLI
gemini skills install https://github.com/browser-use/browser-use --path skills/cloudManually: put the files in place
.devin/skills/cloud/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add browser-use/browser-use --skill cloud -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set4
The whole set →Similar
Questions about cloud
How do I install cloud in Claude Code?
Run npx skills add browser-use/browser-use --skill cloud -a claude-code, run npx skills add browser-use/browser-use --skill cloud -a claude-code again, and check ~/.claude/skills/cloud/SKILL.md.
What does the cloud skill do?
It provides Browser Use Cloud documentation for the REST API, SDKs, cloud browsers, sessions, profiles, CDP, and integrations. It supports Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode.
Does cloud cover the open-source Browser Use library?
No. This skill covers the hosted API and SDK for Browser Use Cloud. Use the open-source skill for the Python library with Agent, Browser, and Tools.
Source text
SKILL.md · MIT
---
name: cloud
description: >
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.
allowed-tools: Read
---
# 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](https://browser-use.com/pricing.md). Use `gpt-5.6-luna` for the free starter; paid-only models need a top-up.
Reuse `BROWSER_USE_API_KEY`, or guide the user through Cloud signup and key creation. Keep keys server-side, never in prompts or client bundles.
## API & Platform
| Topic | Read |
|-------|------|
| Current v4 setup, first run, sessions, workspaces, browsers | `references/api-v4.md` |
| Legacy v2 setup, pricing, FAQ | `references/quickstart.md` |
| v2 REST API: all 30 endpoints, cURL examples, schemas | `references/api-v2.md` |
| v3 BU Agent API: sessions, messages, files, workspaces | `references/api-v3.md` |
| Sessions, profiles, auth strategies, 1Password | `references/sessions.md` |
| CDP direct access, Playwright/Puppeteer/Selenium | `references/browser-api.md` |
| Proxies, webhooks, workspaces, skills, MCP, live view | `references/features.md` |
| Parallel, streaming, geo-scraping, tutorials | `references/patterns.md` |
## Integration Guides
| Topic | Read |
|-------|------|
| Building a chat interface with live browser view | `references/guides/chat-ui.md` |
| Using browser-use as a subagent (task in → result out) | `references/guides/subagent.md` |
| Adding browser-use tools to an existing agent | `references/guides/tools-integration.md` |
## 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: <key>`
- Get API key: https://cloud.browser-use.com/new-api-key
- Set env var: `BROWSER_USE_API_KEY=<key>`
- Cloud SDK: `uv pip install browser-use-sdk` (Python) or `npm install browser-use-sdk` (TypeScript)
- Python v2: `from browser_use_sdk import AsyncBrowserUse`
- Python v3: `from browser_use_sdk.v3 import AsyncBrowserUse`
- Python v4: `from browser_use_sdk.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"`
- SDK 3.11.3 or newer exposes `browsers.create` and `browsers.stop` in the v4 namespace, alongside the v4 REST `/browsers` resource. Always stop a browser explicitly; closing CDP does not stop billing.
- CDP WebSocket: `wss://connect.browser-use.com?apiKey=KEY&proxyCountryCode=us`
© browser-use · MIT · browser-use/browser-use