Skip to main content
Use CDP when an external browser framework needs protocol control over a Webcompute browser.

Get a CDP URL

You can attach CDP-compatible tools such as Playwright, Puppeteer, Stagehand, Browser Use, or custom clients when they fit your workflow.

Attach Playwright over CDP

Playwright CDP attachment is useful for interop. For agent-readable observations after each step, prefer Webcompute browser-code execution or MCP execute_playwright_code.
CDP URLs are signed bearer capabilities. Share them only with systems that should control the browser.

Observation boundary

Direct CDP clients do not automatically receive Webcompute post-step observations. Use SDK browser-code execution, MCP execute_playwright_code, or runtime status endpoints when an agent needs bounded page evidence after each step.

When to use CDP

  • Attach an existing browser framework.
  • Inspect low-level protocol behavior.
  • Reuse a known CDP workflow.
  • Run deterministic checks outside the agent harness.
For most TypeScript product workflows, start with SDK quickstart. For coding-agent hosts, start with MCP.