Archive downloads with run evidence
Connect
SPIRITT
BrowserbaseBrowserbase
Run browsers with purpose
SPIRITT manages the operation around your headless browsers: session setup, failure investigation, download delivery, and resource tracking. Turn individual browser runs into systems your team can rely on.
What you can do with Browserbase.
Failures with evidence
Connect session status and network logs to actionable investigations, with live debug links when a browser run needs attention.
Downloads delivered
Collect completed session artifacts, route them to connected storage, and clean up session downloads under your retention rules.
Resource accountability
Bring project browser minutes, proxy consumption, and session activity into one view so teams can make informed automation decisions.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the browser automation operations you want built and maintained.
02
Connect Browserbase
Connect Browserbase with your API key and identify the projects, sessions, and browser contexts the mission should manage.
03
Delegate an outcome
Ask SPIRITT to build a session control desk, investigate failing runs, or operate download delivery across your connected tools.
Hand over a mission.
Choose a mission. Make it yours.
Put Browserbase to work.
Put browser operations on track
Questions
Browserbase, with SPIRITT.
01What can SPIRITT manage directly in Browserbase?+
SPIRITT can list projects and sessions, create sessions, retrieve session details and logs, obtain live debug URLs, and request session completion. It can also manage browser contexts and uploaded extensions, upload files to sessions, retrieve downloads, and track project usage.
02What access does the connection need?+
Browserbase connects with an API key. Specify the projects and resources SPIRITT should operate on, along with any rules for ending sessions or deleting stored data. Access to a target website is separate from access to Browserbase and still requires the appropriate authorization.
03Can it operate recurring browser workflows?+
Yes. SPIRITT can schedule session checks, download collection, usage tracking, and policy-based cleanup. For workflows that navigate pages or interact with websites, it can coordinate an authorized browser runner and manage the Browserbase sessions and evidence around that execution.
04How can Browserbase work with my other tools?+
Session artifacts can be delivered to Google Drive, usage snapshots recorded in Google Sheets, and failure evidence carried into Linear issues. Slack can receive live debug links and operational summaries, while Supabase can hold a searchable run ledger for a custom application.
05What useful applications can SPIRITT build around Browserbase?+
Useful builds include a session control desk, a browser usage dashboard, a download delivery service, and a test evidence library. These applications combine Browserbase session metadata, logs, artifacts, and usage statistics with your job definitions, ownership rules, and retention policies.
06Does this connection itself click through websites?+
The provided Browserbase actions manage browser infrastructure rather than expose page-clicking or navigation commands. Browserbase supports browser runners such as Playwright, Puppeteer, and Selenium. SPIRITT can build the wider workflow around a runner, keeping session management distinct from the code that interacts with pages.