Capture Browser Sessions now support Chrome DevTools Protocol (CDP), giving you direct, low-level browser control from your existing automation tools.
Instead of being limited to Capture’s session actions API, you can now create a CDP-enabled browser session and connect to it using Playwright, Puppeteer, or any CDP-compatible client.
What’s new
- Create Browser Sessions with CDP enabled
- Receive a secure
connectUrlfor the lifetime of the session - Connect using standard CDP clients like Puppeteer or Playwright
- Keep the benefits of Capture-managed infrastructure, including hosted browsers, session lifecycle management, proxy support, and automatic cleanup
- Use advanced browser automation features that require direct DevTools access
Why it matters
CDP support makes Capture Browser Sessions much more flexible for teams building advanced browser workflows.
You can now use Capture when you need managed browser infrastructure, but still keep direct protocol-level control for use cases like:
- Complex interaction flows
- Custom scraping logic
- Browser instrumentation
- Network inspection
- Performance tracing
- Advanced page automation
- Existing Puppeteer or Playwright workflows
Example
Create a CDP-enabled session:
{
"cdp": true
}
The session response includes a connectUrl:
{
"session": {
"id": "sess_...",
"status": "active",
"connectUrl": "wss://..."
}
}
Then connect with your CDP-compatible client and drive the browser directly.
