browser-use CLI in the agent’s environment and it can drive a stealth cloud browser — with proxies, CAPTCHA solving, live view, and recording. Your API key stays in a credential vault; the model never sees it.
The sandbox only ships a bare headless Chromium for Playwright: no stealth, no proxies, no CAPTCHA handling. So the agent starts a named Browser Use Cloud browser and drives it with browser-use <<'PY' Python snippets.
Create the vault and its credential in the Claude Console. Create the environment and agent there too, or save their YAML blocks as environments/browser-env.yaml and agents/browser-agent.yaml and run ant apply on each, which prints the ID. Save the IDs as ENVIRONMENT_ID, VAULT_ID, and AGENT_ID.
1. Create an environment
Pre-install the CLI so it’s ready at session start (no runtime install).2. Create a credential vault
Store your key as an environment variable so the CLI reads it and the model never does. Get one at cloud.browser-use.com/settings.
The CLI sends the key in a request header, so the Console default (header injection only) works.
3. Create the agent
Tell it to use the CLI in cloud mode.4. Start a session and send a task
Create a session that uses the agent, the environment, and the vault.user.message event (or test it from the Console’s session runner).
5. Watch it run
The agent starts a named cloud browser, runs Python helper snippets throughbrowser-use, then returns the result. The browser shows up in cloud.browser-use.com with a Live View. For an mp4 recording, have the agent call start_remote_daemon("managed", enableRecording=True).
If a session ends before the agent runs stop_remote_daemon, the browser keeps running until its timeout (60 minutes by default). Stop it from the dashboard, or pass a shorter timeout= in minutes to start_remote_daemon.