cookie-sync

The cookie-sync skill solves the challenge of accessing authenticated websites through Browserbase cloud sessions by seamlessly transferring your local Chrome browser cookies to a persistent Browserbase context. When you need to automate tasks on sites where you're already logged in—like Gmail, Twitter, or internal tools—manually re-authenticating in cloud sessions is tedious and sometimes impossible. This skill exports your active Chrome session cookies and injects them into a Browserbase persistent context, allowing the browse CLI to interact with those sites as if you were logged in.

Key features include domain filtering to sync only the cookies you need (avoiding unnecessary data transfer), context reuse to refresh expired cookies without creating new contexts, and advanced options like verified browser mode and residential proxy support. The skill connects to Chrome via the Chrome DevTools Protocol (CDP), extracts cookies, and uses the Browserbase API to create or update persistent contexts. It supports all Chromium-based browsers including Brave and Edge, requires Chrome's remote debugging to be enabled, and works with Node.js 22+.

This skill is designed for developers and automation engineers who need to run authenticated browser sessions in cloud environments for testing, monitoring, data collection, or scheduled tasks. Common use cases include accessing authenticated APIs through browser sessions, running automated workflows on sites that require login, testing user-specific features in cloud CI/CD pipelines, and maintaining long-running scheduled jobs that interact with authenticated web services. By separating the one-time cookie sync (done on your laptop) from the recurring automated tasks (run in Browserbase), you can build robust, authenticated automation without storing credentials or managing complex login flows.