Sanaf AI
Start free
Developer Tools

Browserbase, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Browserbase account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Connects with a key
  • 10 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Browserbase is

Browserbase is a serverless platform that enables developers to run, manage, and monitor headless browsers at scale, offering seamless integration with tools like Playwright, Puppeteer, and Selenium.

You paste in a key from your own Browserbase account. It is kept encrypted, and you can withdraw it from inside Browserbase whenever you like.

How a run works

One message in, the work done in Browserbase.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Browserbase. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Browserbase account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

10 tools it already has

What it can do in Browserbase

These are the ready-made tools your AI employee already has in Browserbase. It is not limited to them, but it never has to be taught these.

  • Create a new browser contextTool to create a new browser context. use when you need to obtain upload credentials for a custom user-data-directory in a project.
  • Create Browser SessionTool to create a new browser session. use when you need an isolated browser context before performing any page interactions.
  • Download Session ArtifactsTool to download files from a specific session. use after session completion to retrieve all generated artifacts in a zip archive.
  • List Browser SessionsTool to list all browser sessions. use when you need to retrieve sessions with optional filtering by status or metadata query.
  • Retrieve a browser contextTool to retrieve details of a specific browser context. use when you have a context id and need its metadata.
  • Retrieve a browser sessionTool to retrieve details of a specific browser session. use when you have a session id and need its metadata (status, urls, timestamps).
  • Retrieve Session Debug URLsTool to retrieve live debug urls for a specific session. use when you need to connect to a running session for debugging.
  • Retrieve Session LogsTool to retrieve logs of a specific session. use after actions in a session to inspect network events and data exchange.
  • Update Browser ContextTool to update a specific browser context. use when you need fresh upload url and encryption details for an existing context, after obtaining a valid context id.
  • Update Browser SessionTool to update the status of a specific browser session. use when you need to request session completion before timeout to avoid additional charges.
Access, and who is in charge of it

You stay the boss of your Browserbase account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Browserbase account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Browserbase is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Browserbase and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Browserbase

Can an AI employee really work inside Browserbase?
Yes. It signs in to your own Browserbase account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Browserbase?
No. Nothing moves and nothing is replaced. Your records stay in Browserbase, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Browserbase account?
You paste in a key from your own Browserbase account. It is kept encrypted, and you can withdraw it from inside Browserbase whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Browserbase?
It has 10 ready-made tools in Browserbase today, among them Create a new browser context, Create Browser Session and Download Session Artifacts. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Browserbase and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Browserbase and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Browserbase?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Browserbase is written down with what it did and when.