Browser Tools SDK | Libretto

Libretto

2 min read Original article ↗

// BROWSER TOOLS SDK --

Give your agent a browser.

Six tools let any AI agent open a real browser, read the page, and act with Playwright.

$npm i libretto-browser-tools

// BENCHMARKS --

55% lower cost than alternatives

Lets your agent work through complex pages with less overhead — and a lot less cost.

// INTEGRATIONS --

Use the agent stack you know.

Built-in adapters for AI SDK, Pi, and MCP, plus a custom path for anything else. More frameworks are on the way.

// HOW IT WORKS --

Two tools do most of the work.

The agent reads a short page snapshot, then runs the Playwright code it needs.

// MORE FROM LIBRETTO --

Build and repair browser workflows.

// FAQ --

Common questions

Which integrations work today?+

The package includes adapters for AI SDK, Pi, and MCP. The base tools are framework-neutral, so you can also wire them into your own agent loop.

Which browser providers can I use?+

Run Chromium on your machine with LocalBrowserProvider, or use the built-in providers for Libretto Cloud, Browserbase, Kernel, and Steel.

Why does the SDK expose only six tools?+

Most browser work needs two tools: browser_snapshot to read the page and browser_exec to run Playwright. The other four tools open, connect, inspect, and close browser sessions.

Does Browser Tools SDK replace Playwright?+

No. It gives an agent a small tool set and runs its browser_exec code through Playwright. You still have the Playwright API.

Is Browser Tools SDK open source?+

Yes. The package is available under the MIT license in the Libretto repository.

// GET STARTED --

Add browser tools to your agent.

Install the package. Keep your current model and agent framework.

$npm i libretto-browser-tools

VIEW SOURCE ON GITHUB →