Browser Use

Browserbase

Run browser sessions on Browserbase's cloud infrastructure, with anti-detection features, residential proxies, and persistent contexts.

When to use Browserbase

Choose Browserbase when:

The task needs stealth: advanced stealth mode uses a custom Chromium build designed to avoid bot detection on sites that block standard headless browsers.
The task needs residential proxies: routing traffic through residential IP addresses reduces CAPTCHA challenges and IP-based rate limiting, with geo-targeting to specific countries, states, or cities.
Sessions should persist in the cloud: Browserbase contexts keep cookies and storage across sessions, so an agent can resume where it left off.
Gamut runs on a server: on headless servers where Chrome is not installed, Browserbase provides browser access without local dependencies.

For straightforward tasks on sites without aggressive bot detection, the built-in browser is simpler and has no additional cost. For tasks that need your local Chrome profiles and cookies, use Chrome integration.

Setup

Setup takes one of two paths: bring your own Browserbase account, or use the Platform-managed option.

Bring your own account

Sign up at browserbase.com and create a project.
Open Settings > Browser in Gamut.
Set Browser Host to Browserbase.
Enter your API Key and Project ID in the fields that appear.
Click Connect. Gamut validates the credentials against the Browserbase API before saving them.

A green "Credentials saved" badge appears once validation passes. Saved credentials can be updated or removed at any time.

Credentials can also come from environment variables instead of the settings UI:

BROWSERBASE_API_KEY
BROWSERBASE_PROJECT_ID

Environment variables take effect without entering anything in the UI; the settings page shows "Using environment variable" when they are in use.

Platform-managed

With a Gamut Platform account signed in, the Platform browser host option becomes available. It uses Browserbase through the Platform's managed proxy, so no separate API keys are needed, and your Platform subscription covers the browser session costs. The same session settings (stealth mode, proxies) apply.

Session settings

Both the Browserbase and Platform-managed hosts support the following settings, configurable in Settings > Browser.

Advanced stealth mode

When enabled, Browserbase uses a custom Chromium browser with modifications to avoid common bot detection techniques, so the browser appears more like a regular user's to anti-bot services.

An optional Operating System selection changes the user-agent string and browser environment signals to match the chosen platform: Default (auto), which lets Browserbase choose, plus Linux, Windows, macOS, Mobile, and Tablet.

Advanced stealth mode requires a Browserbase Scale plan.

Proxy configuration

When proxies are enabled, browser traffic routes through Browserbase's residential proxy network. This helps with:

Avoiding IP-based rate limiting and blocks.
Higher CAPTCHA success rates.
Accessing geo-restricted content.

An optional proxy location narrows where traffic exits:

Field	Format	Example
Country Code	Two-letter ISO code	`US`
State	Two-letter state code	`NY`
City	City name in uppercase	`NEW_YORK`

Leave all location fields empty for Browserbase's default (best-effort US proxy).

Persistent contexts

Each agent gets its own Browserbase context: a store of cookies, local storage, and session storage that carries across browser sessions.

A login in one session remains active the next time the agent opens the browser.
Agents do not share session data with each other.
Contexts are stored in Browserbase's infrastructure and persist until you delete them.

Gamut saves the context-to-agent mapping locally and reuses it across sessions.

How it works

When an agent opens the browser with Browserbase selected:

Gamut creates (or reuses) a Browserbase context for the agent.
A new Browserbase session is created with keepAlive enabled, so the session survives temporary disconnections.
Gamut connects to the session via its debug WebSocket URL, which supports multiple simultaneous connections (unlike the single-use connect URL).
The browser panel in the Gamut UI streams frames from the remote browser, just as it does for local browsers.

If an existing session is still running when the agent opens the browser again, Gamut reuses it instead of creating a new one.

Tradeoffs vs. the built-in browser

Aspect	Built-in Browser	Browserbase
Setup	None; works out of the box.	Requires a Browserbase account or Platform subscription.
Cost	Free (included with Gamut).	Browserbase charges per session minute.
Bot detection	Standard headless Chromium; may be blocked by some sites.	Advanced stealth mode with custom Chromium build.
Proxies	No proxy support.	Residential proxies with geo-targeting.
Latency	Low; the browser runs locally in the container.	Higher; the browser runs on remote infrastructure with network overhead.
Local access	Cannot access host `localhost`.	Cannot access your local network.
Persistent state	Profile persists within the container.	Context persists in Browserbase's cloud across sessions.
Dependencies	None.	Network connection to Browserbase API and WebSocket endpoints.

Troubleshooting

"API key not configured": enter both the API key and project ID in Settings, or set the corresponding environment variables.
"Failed to create Browserbase session": check that the API key is valid, the Browserbase project exists, and the account has available session capacity.
Stealth mode not working: advanced stealth mode requires a Browserbase Scale plan. Check your Browserbase account tier.
Proxy location not taking effect: verify that the country code is a valid two-letter ISO code and that Browserbase has proxy coverage in the requested location.