Skip to main content
Use manage_browser_pools when your agent needs the same browser setup more than once. A pool keeps pre-warmed browsers ready with the profile, viewport, proxy, extension, Chrome policy, and start URL you choose, so the agent can acquire a session without waiting for a fresh browser to boot. Create the pool outside the hot path of your agent workflow. During the task, acquire a browser, control it with computer_action or execute_playwright_code, then release it back to the pool when the browser can be reused.
Browser pools are available on Start-Up and Enterprise plans. See Pricing for availability and Browser Pools for SDK examples.

Actions

  1. Call create with the browser configuration your repeated task needs.
  2. Call list to find an existing pool, or get when you need the full pool configuration.
  3. Call acquire before browser control.
  4. Use the returned session_id with computer_action, execute_playwright_code, browser_curl, or exec_command.
  5. Call release with reuse: true when the session can return to the pool, or reuse: false when it needs to be replaced.
  6. Call update when you need to resize the pool or change its browser configuration.

Parameters

Response behavior

create and update return a compact browser_pool summary plus next_actions. The next actions use the stable pool id, so agents can follow up without relying on the display name. list returns compact pool summaries and a note to call get for full details. acquire returns a compact browser summary plus next actions for controlling, releasing, and inspecting the acquired browser.

Create a checkout pool

Update idle capacity

Acquire and release a browser