Pass a proxy configuration object when launching the browser: set the server field to your proxy URL (e.g., http://YOUR_PROXY_HOST:YOUR_PROXY_PORT).
If the proxy requires authentication, add username and password fields to the proxy object using short placeholder values such as YOUR_PROXY_USER and YOUR_PROXY_PASS.
Use the bypass field to specify a comma-separated list of hostnames or IP ranges that should bypass the proxy.
Verify the proxy is applied by navigating to an IP-checking endpoint and confirming the expected egress IP.
For per-context proxy settings, pass the proxy object to browser.newContext() rather than to browserType.launch() to scope it to specific contexts.
Test with all three browser engines (Chromium, Firefox, WebKit) as proxy behavior can differ between them.
Known gotchas
Proxy credentials are passed as structured fields in the proxy configuration object — do not embed them directly in the proxy server URL as this may not be supported by all engines.
The bypass list syntax differs slightly between browser engines; test thoroughly if you rely on host-specific bypass rules.
HTTPS proxies (proxies that themselves use TLS) require additional certificate trust configuration that is distinct from plain HTTP proxy setup.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp