feat: add ChromeDriver proxy for WebDriver and BiDi protocol support

[tnsardesai]

Install ChromeDriver matching the Chromium version in both headful and headless images, managed via supervisord on internal port 9225. A new ChromeDriver proxy (exposed on port 9224) intercepts session creation to inject goog:chromeOptions.debuggerAddress so ChromeDriver attaches to the already-running browser (at port 9222), rewrites webSocketUrl in responses to route BiDi traffic back through the proxy, and transparently proxies all other HTTP and WebSocket traffic.

Extracts the shared WebSocket bidirectional pump logic from devtoolsproxy into a reusable wsproxy package with a MessageTransform hook, used by both the existing DevTools proxy and the new ChromeDriver proxy. Expands CDP discovery endpoint proxying to include /json/list and makes proxy ports configurable via environment variables.

Includes comprehensive unit tests for the ChromeDriver proxy and manual BiDi validation scripts (raw WebSocket, Puppeteer, Selenium).

Checklist

• A link to a related issue in our repository
• A description of the changes proposed in the pull request.
• @mentions of the person or team responsible for reviewing proposed changes.

---

Note

Medium Risk
Moderate risk because it adds a new externally exposed ChromeDriver proxy/port and rewrites WebDriver/BiDi session payloads, which can break existing automation clients or routing if misconfigured.

Overview
Adds first-class WebDriver/BiDi support via ChromeDriver. The Chromium headful/headless images now install a matching chromedriver, run it under supervisord on 127.0.0.1:9225, and expose a new public port 9224 for ChromeDriver access.

Introduces a Go ChromeDriver proxy that intercepts POST /session (and BiDi session.new) to inject goog:chromeOptions.debuggerAddress pointing at the DevTools proxy, rewrites returned capabilities.webSocketUrl to route BiDi back through the proxy, and otherwise reverse-proxies ChromeDriver HTTP/WebSocket traffic.

Refactors and hardens proxy plumbing. DevTools proxy ports become configurable (DEVTOOLS_PROXY_PORT, CHROMEDRIVER_PROXY_PORT, etc.), DevTools JSON discovery proxying is generalized to also cover /json/list with recursive URL rewriting, and the shared WebSocket pump is extracted into a reusable wsproxy package.

Testing/ops updates. Adds unit tests for JSON rewriting and ChromeDriver proxy behavior, new BiDi e2e tests plus Node-based validation scripts, and updates e2e container helpers to map/wait on the new ChromeDriver port.

^{Written by Cursor Bugbot for commit 62f0fc5. This will update automatically on new commits. Configure here.}

[hiroTamada]

Clean, well-structured addition of ChromeDriver/BiDi support. The proxy design is minimal — only intercepts session creation and WebSocket URL rewriting. Good extraction of the shared wsproxy package, and solid test coverage across unit, integration, and real e2e with Puppeteer/Selenium/Vibium. Left two minor nits on the wrapper scripts.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}