Skip to main content
Browser Use’s cloud browsers speak Chrome DevTools Protocol (CDP) over a remote WebSocket. Selenium can’t consume that natively: its debugger_address option only supports local host:port connections, not remote wss:// URLs. You have two practical paths. If you’re migrating Selenium scripts, connect through Playwright’s sync API — the page-automation model (navigate, locate, click, read) maps one-to-one, and you get the hardened stealth Chromium and residential proxies with no configuration.
Common Selenium → Playwright equivalents:

Query parameters

Alternative: keep Selenium with a local proxy

If you must keep the Selenium API, run a local WebSocket-to-TCP proxy so Chrome’s remote debugging endpoint appears as a local host:port, e.g. via selenium-wire. This adds a moving part we don’t manage — for new code, prefer the CDP bridge above.
Selenium’s debugger_address only supports local host:port connections. For remote CDP over WebSocket, use Playwright or Puppeteer instead.
Always stop browser sessions when done. Sessions left running will continue to incur charges until the timeout expires.

See also