setup-browser-cookies

Import cookies from real browsers into Playwright test sessions.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AndrewLi0420/BMW --skill setup-browser-cookies-andrewli0420
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/AndrewLi0420/BMW/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/AndrewLi0420/BMW --skill setup-browser-cookies-andrewli0420

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser into a headless browse session to enable authentic QA testing without re-login.

Core Features & Use Cases

  • Import cookies from Comet, Chrome, Arc, Brave, or Edge into a Playwright session.
  • Open an interactive picker UI to select which cookie domains to import before testing authenticated pages.
  • Use during QA/test automation when you need to simulate logged-in scenarios across multiple sites.

Quick Start

Open the cookie importer, choose the domains to import, and run your tests with an authenticated browser session.

Frequently Asked Questions about setup-browser-cookies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import browser cookies into Playwright for authenticated QA testing?

To import browser cookies for authenticated QA testing, you can use a tool that decrypts and loads cookies from your local browser profile directly into a Playwright headless session. This enables logged-in test flows without manual re-authentication.

Does Playwright support importing cookies from Chrome, Arc, Brave, or Edge?

Playwright can use imported cookies from Chrome, Arc, Brave, or Edge by decrypting the local browser profile data. The process extracts the authentication cookies and loads them into the test session to simulate logged-in user states.

What is the best way to automate authenticated test sessions across multiple domains?

Automating authenticated test sessions across multiple domains is best handled by selectively importing cookies from a real browser. You can use an interactive picker to choose specific cookie domains and load them into your testing pipeline.

How do I select specific cookie domains to load into my automation pipeline?

You can select specific cookie domains for your automation pipeline by using an interactive picker UI. This interface allows you to choose exactly which authenticated domains to import before executing your end-to-end test runs.

Why do my headless test sessions fail to maintain authenticated states across multiple sites?

Headless test sessions fail to maintain authenticated states because they lack the session cookies stored in your real browser. Decrypting and importing these cookies from your local browser into the test session resolves this authentication gap.