Browser Use Proxy Settings: Local and Cloud

import os
from browser_use import Browser
from browser_use.browser.profile import ProxySettings

# Configuration for a locally launched browser.
# This fragment does not start an agent or call a model.
browser = Browser(
    proxy=ProxySettings(
        server=os.environ['PROXY_SERVER'],
        username=os.environ['PROXY_USERNAME'],
        password=os.environ['PROXY_PASSWORD'],
    )
)
# Pass browser to your Agent configuration.
# Keep these credentials out of the task prompt.

Browser Use exposes proxy settings on its browser configuration. If you are evaluating it with an external provider, first identify where the browser runs. A locally launched browser, a browser reached through CDP and a managed cloud browser can require different setup steps.

The browser owns the proxy connection

The open-source browser reference documents ProxySettings with a server address, bypass list and optional username and password. It separately documents cdp_url for connecting to an existing browser. Those settings answer different questions: which browser to control, and how its traffic should leave the network.

Keep proxy credentials in the browser configuration. They should not be placed in the agent's task prompt. A task such as “check this public page” does not require the language model to read a proxy password.

Choose local or hosted execution deliberately

The Browser Use quickstart describes installing the Python package and browser, choosing a model and running an agent. That is a useful baseline for a local evaluation. Record the package version and model configuration so a later change can be investigated.

If you switch to a managed browser, check the cloud product's current configuration contract and billing separately. Do not copy a local browser setting into a remote connection and assume that it changes an already-running browser's network route.

The Proxies.sx Pool Gateway documentation is the starting point for obtaining connection details.

Design a test an agent cannot accidentally expand

1. Use a read-only task on a page you control or are authorized to access.
2. Load a diagnostic page through the browser and record the observed network address privately.
3. Run one short task with a clear completion condition. Keep the target and instructions fixed when comparing routes.
4. Repeat with a fresh profile, then with retained state if the workflow requires it. Record which setting changed.
5. Review the resulting page or extracted fields. A model's statement that it succeeded needs an observable result.

Set a spending limit for the evaluation that covers the model, browser hosting where applicable, and proxy traffic. Report the cost per completed task alongside failures; a count of attempted tasks alone hides retries.

What a proxy changes

A proxy changes the network route. It does not supply a browser fingerprint, change its rendering engine or make an agent behave like a human. Test the browser configuration and the network route as separate variables.

Separate website text from task instructions

Pages can contain text that asks an agent to change its task or disclose information. Keep the original task and permitted actions clear. Review proposed purchases, messages or account changes before allowing a browser agent to perform them. Proxy routing does not change the authority of text found on a page.

Does a proxy make an agent's browsing anonymous?

No. Cookies, account identity and browser state still matter. Choose a proxy for the routing requirement you can test.

Use the proxy evaluation guide to record results. Developers and agent operators can continue to Proxies.sx agent documentation.