> ## Documentation Index > Fetch the complete documentation index at: https://browseruse-0aece648-codex-docs-supported-exports.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > 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; V2 is the lower-cost option for simple tasks. Keep V3 examples explicitly versioned. The open-source browser-use library and hosted browser-use-sdk have different APIs. > 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 / $200 / $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. > Budget polling across the project: the standard general bucket is 25 requests/second, including V4 event reads and full run reads. Selected status reads have a separate higher bucket. Use bounded workers, stagger polls, respect Retry-After, and drain hasMore event pages after terminal status. A busy V4 session returns 409; its queue holds 10 pending messages and is not a project-wide batch queue. > A completed run or closed CDP connection does not immediately stop its cloud 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. # Which Browser Use do I need? > Run Browser Use on your machine, run the full stack in our cloud, or bring your own agent and use only the hosted browser. Pick where your agent and browser should run. On your computer, choose Claude Code, Codex, OpenCode or Hermes Agent, then Playwright CLI or Browser Use CLI. Either CLI can use real Chrome or the single Cloud Browser. A separate Profile Sync step copies selected cookies from real Chrome to a cloud profile. Hosted V4 runs OpenCode, Browser Use CLI and Cloud Browser: send a prompt, get a result. On your computer, choose Claude Code, Codex, OpenCode or Hermes Agent, then Playwright CLI or Browser Use CLI. Either CLI can use real Chrome or the single Cloud Browser. A separate Profile Sync step copies selected cookies from real Chrome to a cloud profile. Hosted V4 runs OpenCode, Browser Use CLI and Cloud Browser: send a prompt, get a result. ## On your computer Claude Code, Codex, OpenCode, Hermes Agent, or another local agent can run the [Browser Use CLI](https://docs.browser-use.com/open-source/browser-use-cli) on your computer. Local computer-use CLIs such as Playwright CLI and Agent Browser fit the same shape. They can control real Chrome, with its tabs and logins, or use the single hosted browser shown in our cloud. Start with real Chrome. Connect to our cloud when a site blocks you or you need many browsers at once. Run `browser-use auth login` once before the first cloud connection. [Profile Sync](/cloud/guides/profile-sync) copies selected cookies from real Chrome into a cloud profile. Run it explicitly for the accounts you want to use in the cloud; the dashed line does not mean automatic synchronization. ## In our cloud [Cloud v4](/cloud/quickstart) runs OpenCode, Browser Use CLI and Cloud Browser. You send a prompt to our API and get the result back, plus a live preview and any files it produced. Nothing runs on your computer. Use the full hosted stack for scheduled work, tasks your users trigger, and work that should keep running without your computer. ## Only the browser Use the [Browser API](/cloud/browser/quickstart) when you only need the hosted browser. Browser Use CLI or a custom computer-use CLI can connect to the same Cloud Browser from your computer or your own cloud; Browser API does not add a hosted agent. One API key from [cloud.browser-use.com/settings](https://cloud.browser-use.com/settings?tab=api-keys\&new=1) works for all three. Credits and profiles live in the same project.