Agent

Browser

Browser gives an agent a managed web browsing session for tasks that need live pages, interactive websites, or visual context. Turn on browser when the agent needs to inspect or operate a site the way a person would.

Browser works without a proxy

You do not need to configure a proxy for normal browsing. If browser is enabled for the agent, the browser session should work on its own. Add a proxy only when the agent must browse through a specific server, network, region, or customer-approved route.

How to use browser

01Ask your agent to use a browser. It should just work.
02In the Browser tab, add and enable a proxy only if the agent must browse through a specific server or network.

What browser is for

Research: Open current pages, inspect sources, and gather up-to-date public information.
Web app workflows: Navigate forms, dashboards, and authenticated sites when a tool integration is not available.
Visual verification: Check page state, screenshots, layouts, or browser-only behavior.

Proxies are optional

Most agents do not need a proxy. Use the browser without one unless traffic must come from a specific server, network, region, or customer-approved route. A proxy changes where the browser session's traffic exits; it does not turn browser access on.

When a proxy is required, add it in the Browser area. Each proxy has a name, server, and optional username and password. Only one proxy can be active at a time; if you enable one proxy, Brainbase disables the others for that agent.

Field	Required	Description
Name	Yes	A readable label for the proxy.
Server	Yes	The proxy server URL or host your browser traffic should use.
Username	No	The proxy username, if the proxy requires authentication.
Password	No	The proxy password, if the proxy requires authentication.

When to use browser

Use browser when the agent must interact with a real web page or inspect rendered content. Use tools or MCP servers instead when a structured API can provide the same data more reliably.

Best practices

Prefer API tools for high-volume or repeatable data access.
Start without a proxy; add one only when routing requirements demand it.
Keep proxy credentials in Secrets or the proxy credential fields, not in instructions.
Enable only the proxy the agent should currently use.
Review browser sessions for agents that interact with sensitive customer systems.
Give the agent clear instructions about which sites it may access and what actions require confirmation.