Skip to main content
A managed browser is the runtime behind Webcompute agent runs, SDK workflows, MCP tools, REST calls, quick actions, and CDP attachments. It gives browser work concrete handles:
  • Lifecycle: create, inspect, stop, resume, close.
  • Capabilities: Debug UI URL, CDP URL, recording support, CAPTCHA status, and other runtime affordances.
  • Policy: domain boundaries and runtime configuration.
  • Visibility: Debug UI, recordings, status, and events.
  • Resources: files, downloads, dialogs, and permissions.
  • Control: agent runs, deterministic execution, or CDP attachment.
Most users meet managed browsers through web agent or web.agent(). You only need direct browser lifecycle APIs when your application owns the orchestration.

Lifecycle map

Capabilities

Browser capabilities are signed runtime affordances such as Debug UI and CDP URLs. Treat them like credentials because anyone with the URL can inspect or control the browser within that capability’s scope. Use the SDK methods browser.debugUrl() and browser.cdpUrl(), the CLI commands web browser debug and web browser cdp, or MCP manage_browsers actions debug_url and cdp_url when you need those capabilities. Next: browser lifecycle, browser control, and observe and debug.