Autologin with 1Password
You can now log in with real credentials without ever putting them in your code. Connect a 1Password service account once, then reference an item by its op://Vault/Item/field path from inside a session. Browserless resolves the secret server-side, types it into the field, and locks the session down so the value can't be screenshotted or read back.
It works from Puppeteer, Playwright, BrowserQL, and the Browser Agent, so an AI agent can sign in on your behalf while your passwords stay in your vault. Every use is written to an audit log, and the plaintext value never reaches your automation or the logs.
Read the 1Password integration guide →
Datacenter proxies: a faster, lower-cost proxy option
Alongside residential proxies, you can now route traffic through datacenter proxies by adding proxy=datacenter to your connection. They cost 2 units per MB versus 6 units per MB for residential, about a third of the price, and they're faster, which makes them a good fit for sites that don't require residential IPs. Datacenter is selectable across browser sessions, the REST APIs, scraping, and BrowserQL, including right inside the BQL editor and exporter.
const browser = await chromium.connectOverCDP(
"wss://production-sfo.browserless.io?token=YOUR_API_KEY&proxy=datacenter",
);
Upload and download files from your automations
Moving files in and out of a remote browser used to take fiddly workarounds. Two new commands make it simple: Browserless.uploadFile puts a local file into a page for file inputs and upload forms, and Browserless.fileDownloaded hands you back whatever the browser downloads.
The Browser Agent gets this too, so an AI agent can attach a file to a form or pull down a generated report as part of a task, without you scripting the transfer by hand.