setup-browser-cookies

Import browser cookies into a headless Playwright session to preserve login state.

1|3|Updated Mar 19, 2026

Search Tags:#automation #authentication #qa #setup #playwright #browser #cookies

Ready to run

npx skills add https://github.com/ekrishgupta/gemstack --skill setup-browser-cookies-ekrishgupta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/ekrishgupta/gemstack/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/ekrishgupta/gemstack --skill setup-browser-cookies-ekrishgupta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from real browsers into a headless Playwright session to preserve login state during automated QA and testing.

Core Features & Use Cases

Interactive cookie picker UI that lets you choose which cookie domains to import for Comet, Chrome, Arc, Brave, and Edge.
Cookies are decrypted and loaded into the Playwright headless session, persisting across subsequent commands.
It avoids exposing actual cookie values in the UI by showing only domain counts and summary information.

Quick Start

Run the setup-browser-cookies workflow to import cookies from your browser into the headless 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 a Playwright headless session?▼

To import browser cookies into a Playwright headless session, run the setup-browser-cookies workflow to decrypt and load login state from local browsers, preserving authentication across subsequent automated commands.

Can I use cookies from Chrome or Edge for automated QA testing?▼

Yes, you can use cookies from Chrome and Edge for automated QA testing, as the importer supports multiple Chromium-based browsers including Arc and Brave via an interactive domain picker UI.

Do browser cookies persist across multiple Playwright commands?▼

Yes, browser cookies persist across multiple Playwright commands. Once decrypted and loaded into the headless session, the login state is preserved for subsequent automated testing actions without needing reauthentication.

How are cookie values protected during the browser import process?▼

Cookie values are protected during the browser import process by displaying only domain counts and summary information in the interactive UI, preventing the exposure of actual sensitive authentication tokens.

What browsers are supported for importing login state into headless testing?▼

Supported browsers for importing login state into headless testing include Comet, Chrome, Arc, Brave, and Edge. The interactive cookie picker allows you to select specific cookie domains from these Chromium-based browsers.

Do I need a specific binary to set up browser cookies for automation?▼

Yes, you need a one-time browser cookie importer binary and a local UI to set up browser cookies for automation. This requirement enables the decryption and loading of real browser cookies into Playwright.