Browserbase
for LuumenAI
Inspect Browserbase sessions, projects, and usage, then start new work on approval
Connect Browserbase and your headless browser fleet becomes something you can ask about in plain language. Read session lists, logs, debug URLs, project settings, and usage against your quota. When you need a new session, a context, or an extension uploaded, Luumen shows the exact call first and waits for your approval.
The Browserbase toolbox
19 tools: 10 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadRetrieve a browser contextRetrieve details of a specific browser context.
- ReadRetrieve a browser extensionRetrieve details of a specific browser extension.
- ReadRetrieve a projectRetrieve details of a specific project including settings and configuration.
- ReadGet project usage statisticsRetrieve usage statistics for a project including browser minutes and proxy bytes consumed.
- ReadList ProjectsList all projects for the authenticated account.
- ReadRetrieve a browser sessionRetrieve details of a specific browser session.
- ReadRetrieve Session Debug URLsRetrieve live debug URLs for a specific session.
- ReadDownload Session ArtifactsDownload files from a specific session.
- ReadRetrieve Session LogsRetrieve logs of a specific session.
- ReadList Browser SessionsList all browser sessions.
- WriteCreate a new browser contextCreate a new browser context. Approval by default
- WriteUpdate Browser ContextUpdate a specific browser context. Approval by default
- WriteCreate Browser SessionCreate a new browser session. Approval by default
- WriteDelete a browser contextDelete a browser context and all its stored data (cookies, localStorage, etc.). Approval by default
- WriteDelete a browser extensionDelete an uploaded browser extension by its ID. Approval by default
- WriteDelete Session DownloadsDelete all file downloads from a specific browser session. Approval by default
- WriteUpdate Browser SessionUpdate the status of a specific browser session. Approval by default
- WriteUpload Browser ExtensionUpload a browser extension for use in sessions. Approval by default
- WriteUpload File to SessionUpload files to a browser session for file input operations. Approval by default
One prompt, start to finish
What a governed Browserbase run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create a new browser context, update browser context, create browser session, delete a browser context, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Browserbase — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Browserbase to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.