Skip to main content
Use manage_browsers when your agent needs one live browser session to inspect, automate, or debug web state. A created browser runs in an isolated VM and can use profiles, proxies, viewports, extensions, Chrome policy overrides, telemetry, start URLs, and SSH tunneling. For repeated browser work with the same configuration, use Manage Browser Pools instead. Pools reduce startup latency when your agent needs many similar sessions.

Actions

  1. Call list before creating a browser if an existing session might already be active.
  2. Call create with the browser configuration the task needs.
  3. Use computer_action, execute_playwright_code, browser_curl, or exec_command with the returned session_id.
  4. Call update only for session settings that can change after launch, such as profile, proxy, viewport, or telemetry.
  5. Call delete when the task is done. If save_profile_changes is enabled, deleting the browser saves changes back to the selected profile.

Parameters

Response behavior

create and update return structured JSON with browser and next_actions. If you request SSH forwarding, the response includes ssh_port_forwarding with the CLI command, prerequisites, and the URL to use after the tunnel is running. list returns compact browser summaries and omits routine connection details such as cdp_ws_url. Use get with session_id when your agent needs full details.

Create a browser

Update a browser