functions

What This Skill Does

The Browserbase Functions skill allows you to leverage the official bb CLI to deploy and manage serverless browser automation directly in the cloud. By integrating your local development environment with Browserbase, you can move away from managing local headless browsers and instead focus on writing resilient Playwright scripts that execute on Browserbase’s infrastructure. This skill provides a guided path for initializing projects, managing authentication via API keys and project IDs, and deploying code that handles complex web interactions using Playwright-core.

Installation

To integrate this capability into your workflow, install the skill via the OpenClaw command: clawhub install openclaw/skills/skills/peytoncasper/functions. Once installed, ensure you have the pnpm package manager available and your Browserbase credentials configured as environment variables (BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID). You can then initialize a new project by running pnpm dlx @browserbasehq/sdk-functions init my-function to scaffold your environment.

Use Cases

This skill is ideal for developers who need to run automation on a recurring schedule or those requiring a reliable webhook endpoint to trigger browser tasks. It is perfect for cloud-native web scraping, automated testing of dynamic web applications, and performing data extraction tasks that need to run independent of your local machine's uptime.

Example Prompts

1. "Help me initialize a new browser automation project using the Browserbase Functions skill and walk me through the first steps."
2. "I have a Playwright script for scraping data; can you guide me through deploying it to Browserbase using the bb CLI?"
3. "How can I trigger my deployed Browserbase function via a webhook after a specific event occurs?"

Tips & Limitations

When developing, use the pnpm bb dev command to test your functions locally; the dev server supports hot-reloading, which significantly speeds up the iteration cycle. Remember that functions must return JSON-serializable results to be useful for further processing. Be mindful of execution timeouts and ensure your Playwright scripts are optimized to close browser contexts properly to avoid resource leaks. Always store your credentials securely in your .env file and never commit them to version control.