setup-browser-cookies

Import Chromium browser cookies into a Playwright headless session.

Updated Apr 1, 2026

Search Tags:#automation #testing #authentication #qa #playwright #browser #cookie

Ready to run

npx skills add https://github.com/whd4/gstack --skill setup-browser-cookies-whd4

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session.

Core Features & Use Cases

Import cookies from a real browser into a headless session to preserve login state for QA and automation.
Interactive picker UI to select domains to import and manage cookies.
Works with a one-time setup to ensure cookies are available for authenticated testing.

Quick Start

Open the cookie picker and select the domains you want to import for authentication in tests.

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 real browser cookies into a Playwright headless session?▼

You can import real browser cookies into a Playwright headless session by running an interactive picker that discovers your Chromium browser, decrypts existing cookies, and loads them directly into your test context to preserve authentication state.

Can I use my existing Chromium login state for automated QA testing?▼

Yes, you can use your existing Chromium login state for automated QA testing by selecting specific cookie domains through an interactive picker, which then injects those authenticated cookies into your headless browser session.

What is the best way to handle authentication in Playwright tests without storing passwords?▼

The best way to handle authentication in Playwright tests without storing passwords is to import real browser cookies from your local Chromium profile into the headless session, bypassing the need to script login flows or manage credentials.

Does importing browser cookies for headless tests require a one-time setup?▼

Yes, importing browser cookies for headless tests requires a one-time browser discovery setup to locate and decrypt your Chromium profile, after which you can interactively select domains to load cookies into subsequent Playwright sessions.

Why are my authenticated Playwright headless tests failing to maintain login state?▼

Authenticated Playwright headless tests fail to maintain login state because fresh sessions lack session cookies, a problem solved by importing real cookies from a local Chromium browser profile into the test context via an interactive picker.