LangChain on Browserberg
LangChain agents drive Browserberg today through Playwright's toolkit, pointed at a remote CDP endpoint. A first-party integration is on the roadmap and is not shipped.
Things worth knowing
This page describes a roadmap integration
The Playwright route above works now. A first-party LangChain package, and the EU-routed inference gateway that would make model calls stay in the EU too, are both roadmap items.
Credentials should not reach the agent
Put logins in the vault rather than in the prompt or the tool arguments. Placeholder indirection is what keeps a secret out of a model's context window and out of your LLM provider's logs.
Connect in one line
from langchain_community.agent_toolkits import PlayWrightBrowserToolkit
from playwright.sync_api import sync_playwright
p = sync_playwright().start()
browser = p.chromium.connect_over_cdp(
f"wss://browserberg.com/v1/connect?token={token}")
toolkit = PlayWrightBrowserToolkit.from_browser(sync_browser=browser)
tools = toolkit.get_tools()
Details
| Integration status | Community path today; first-party package is roadmap |
|---|---|
| How it connects | PlayWrightBrowserToolkit over a remote CDP endpoint |
| Model routing | Your own keys today; EU inference gateway is roadmap |
| Where sessions run | EU bare metal (OVHcloud) |
As of 2026-08-30
Questions people actually ask
Is there an official Browserberg LangChain package?
Not yet. The Playwright toolkit route above works today; a first-party package is a roadmap item and this page will say so until it is not.
How do I keep credentials out of the agent's context?
Put them in the vault rather than in the prompt or the tool arguments. The model handles a placeholder; the page receives the secret. Anything a tool argument carries ends up in your LLM provider's logs.
Do my model calls stay in the EU?
Today that depends entirely on which keys you configure, because you route the model calls yourself. An EU-routed gateway is on the roadmap; until it exists we would rather you knew that than assumed otherwise.
Other integrations
- Playwright Playwright connects to Browserberg over the Chrome DevTools Protocol.
- Puppeteer Puppeteer talks CDP natively, so connecting to Browserberg is a one-argument change from puppeteer.
- Selenium Selenium reaches Browserberg through Chrome's CDP support.
- Chrome DevTools Protocol If you would rather not use a driver library at all, a session is a plain CDP WebSocket.
- MCP A Model Context Protocol server that exposes Browserberg sessions as tools to any MCP client.
Point an existing script at us
Five browser hours free, no card. If it runs locally, it runs here with one line changed.