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
Recommended flow
- Call
createwith the browser configuration your repeated task needs. - Call
listto find an existing pool, orgetwhen you need the full pool configuration. - Call
acquirebefore browser control. - Use the returned
session_idwithcomputer_action,execute_playwright_code,browser_curl, orexec_command. - Call
releasewithreuse: truewhen the session can return to the pool, orreuse: falsewhen it needs to be replaced. - Call
updatewhen 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.