setup-browser-cookies

Import Chromium browser cookies into a Playwright headless session.

1|Updated Mar 15, 2026

Search Tags:#automation #authentication #playwright #browser #headless #cookies #qa-testing

Ready to run

npx skills add https://github.com/westn/gstack-pi-port --skill setup-browser-cookies-westn

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session. This enables authenticated QA flows by avoiding repeated logins.

Core Features & Use Cases

Open an interactive picker UI to choose which cookie domains to import from your browser
Load imported cookies into the Playwright headless session for immediate authenticated access
Use before QA testing authenticated pages to verify user-specific behavior

Quick Start

Open the cookie picker, select domains to import, and start testing with the loaded cookies.

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 headless Playwright session?▼

To import browser cookies into a headless Playwright session, use an interactive picker UI to select specific cookie domains, which are then decrypted and loaded directly into your test environment for authenticated access.

Why do my authenticated QA tests fail in headless browser automation?▼

Authenticated QA tests fail in headless browser automation because headless sessions start without prior login state. Importing cookies from a real Chromium browser resolves this by preserving active authentication across multiple domains.

Can I use a real Chromium browser profile for Playwright QA testing?▼

Yes, you can use a real Chromium browser profile for Playwright QA testing by selecting and decrypting cookies from your active profile, then loading them into the headless session to bypass repeated login flows.

What is the best way to handle authentication across multiple sites in automated testing?▼

The best way to handle authentication across multiple sites in automated testing is importing domain-specific cookies from a real browser into the headless session, ensuring immediate authenticated access without manual logins.

Do I need to manually log in before every test when using headless browser automation?▼

No, you do not need to manually log in before every test when using headless browser automation. Loading decrypted cookies from your real Chromium browser preserves login state and skips authentication steps.