[Feature Request] Add Browser proxyServer Configuration Functionality #76
Description
Description of Background & Requirement
During front-end development, configuring a proxy server (proxyServer) is a common necessity for solving cross-domain issues, debugging API interfaces, simulating production environment network requests, and other scenarios.
Currently, agent-browser lacks a built-in feature to directly set the browser proxy. This forces developers to manually modify system-level proxy settings or rely on third-party tools, which is cumbersome and may cause unintended side effects to the global network configuration of the device.
Expected Functionality
Add a proxy configuration API/option in agent-browser, supporting basic proxy types: HTTP, HTTPS, SOCKS5.
Allow setting proxy rules with flexibility, including:
Global proxy for all requests
Whitelist/blacklist for specific domains (bypass proxy for internal/local services)
Support dynamic enable/disable of the proxy without restarting the browser instance.
Persist proxy settings (optional) for subsequent project development sessions.
Use Case Example (Front-end Development)
When debugging a local React project that needs to call a remote backend API, we can configure agent-browser to route API requests through a proxy server (e.g., http://127.0.0.1:8080), which effectively bypasses CORS restrictions without modifying system proxy settings.
Additional Context
This feature will greatly improve the development efficiency of developers using agent-browser for front-end project debugging, reducing the cost of network environment configuration.