Use Browserbase from Claude
Add the Browserbase connection to a Space that runs Claude, then use it from every channel in that Space.
Create a Browserbase connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Browserbase connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Browserbase connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Browserbase runs headless browsers in the cloud so teams can automate web tasks with Playwright, Puppeteer, or Selenium without hosting their own browser infrastructure. From type.com, a dev Space can ask Claude to spin up a browser context, start a session, or retrieve and clean up contexts as part of a testing or scraping workflow.
Connect Browserbase once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Create a browser context and session so a new automation run starts with a clean, isolated environment instead of a shared one.
Create a new Browserbase context and session for our nightly checkout test run.
Retrieve a browser context by ID to confirm its configuration before reusing it in a new automation run.
Retrieve the Browserbase context details for context ID bc-5521 before we reuse it.
Delete a context and its stored cookies or local storage once an automation project is finished.
Delete the Browserbase context we used for last month's scraping project.
Creates a browser context and returns the credentials needed to upload a custom user-data directory within a project.
Fetches metadata for a specific browser context by its ID.
Refreshes a browser context's upload link and encryption settings once its ID is already known.
Starts a new isolated browser session, the step before running any page interactions.
Permanently removes a browser context and its stored data, like cookies and local storage.
Browserbase is a platform for cloud browser sessions, browser automation, web search, page fetch, and browser-agent workflows. Official docs cover Browserbase SDKs, REST API references, Playwright/Puppeteer/Selenium access, and Stagehand-based agent automation.
Yes. With a Browserbase connection shared to your Space, Claude can create, check, and clean up browser contexts and sessions directly in a thread.
Browserbase uses an API key you add once to the connection, managed by an admin who decides which Spaces can use it.
Yes. A recurring task, like deleting contexts older than a set age, can be set up as a type.com automation.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Svix to Claude in type.com to create applications, check endpoint status, and manage webhooks from a shared thread.
Connect Swaggerhub to Claude in type.com to manage access control, check API versions, and update portals from a thread.
Connect Swarmsyncai to Claude in type.com to register agents, check username availability, and run marketplace discovery from a shared thread.
Connect Synthflow AI to Claude in type.com to update knowledge bases, attach actions, and manage memory stores for your voice agents.