@browserbasehq/eve package uses Eve’s native extension API. Mount it in an existing agent to add a persistent Stagehand browser with browserbase__run, browserbase__snapshot, and browserbase__screenshot tools.
Prerequisites
- Node.js 24 or newer
- pnpm 10 or newer
- An existing agent on Eve
0.68.xand its model-provider authentication - A Browserbase API key
Install the extension
1
Add the package to your Eve project
2
Mount the extension
Create Configure
agent/extensions/browserbase.ts:BROWSERBASE_API_KEY in the environment where your Eve agent runs. Eve discovers the extension and preserves its runtime dependencies automatically. Your existing agent retains its instructions and model configuration.3
Build and run your agent
Open https://example.com, take a snapshot, and report the page title.Tools
Pass exactly one of
code or actions to run. A snapshot displays IDs like [0-22]; an action uses the inner value, such as { "op": "click", "id": "0-22" }. Refresh the snapshot after navigation or when an ID becomes stale.
Eve’s built-in web_search and web_fetch remain available. The browser extension does not override them.
Configuration
Pass options tobrowserbase() in the extension mount:
Set
BROWSERBASE_PROJECT_ID in the runtime environment to select a non-default Browserbase project. Configure Eve’s agent model and its authentication separately; browser-only calls do not need a separate Stagehand model-provider key.
Session lifecycle
The first browser tool call launches a session. The extension reuses it for later calls and serializes operations. The next call retries failed initialization; healthy sessions survive ordinary tool errors. Callingawait browser.close() inside run releases the owned browser, and the next tool call creates a fresh session.
One Eve process shares browser resources, including pages, cookies, and authentication. Use separate processes for sessions that require isolation. Browserbase sessions use keepAlive: false and the configured session timeout.
Eve extension source
Read the native extension, configuration schema, and lifecycle implementation.

