Remote Agent Browser

remote-agent-browser

Run [agent-browser](https://github.com/vercel-labs/agent-browser) in the cloud with an isolated [Vercel Sandbox](https://vercel.com/docs/vercel-sandbox).

Benchmark

Loading and taking an interactive snapshot of 100 HTTPS pages in a fresh, two-vCPU Vercel Sandbox:

Metric	Result
Execution time (100 pages)	8.01s
Memory (peak, 100 pages)	461.6MB PSS

Execution time includes Sandbox creation. The published time is the median and memory is the maximum from three successful runs using Chromium 151, agent-browser 0.33.2, and `https://example.com/` with a unique query per page. Each page must produce the expected content and interactive snapshot references.

See [the benchmark methodology](./benchmarks/BENCHMARK.md) for details.

Install

pnpm add remote-agent-browser

Use

`AgentBrowser.create()` starts a fresh Vercel Sandbox from the prebuilt browser image. Commands in one client share the same page, cookies, tabs, and element references. `close()` closes Chromium and stops the Sandbox.

Examples

• Capture a screenshot — capture a full-page PNG and save it locally.
• Agent Bash tool integration — let an agent use normal agent-browser invocations through its Bash tool.
• Bypass BotID for trusted automation — pass a Vercel automation bypass token as an origin-scoped header.
• Route traffic through a proxy — configure an authenticated proxy and verify the browser's egress address.

Authentication

Authentication is automatic when running on Vercel through `VERCEL_OIDC_TOKEN`.

For local development, link a Vercel project and pull its environment:

vercel link
vercel env pull .env.local
node --env-file=.env.local examples/screenshot/index.mjs

API

`AgentBrowser.create()`

Starts a fresh browser in a disposable Ve