setup-browser-cookies

Import Chromium cookies into a Playwright headless session for authenticated testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing authenticated pages often requires logging in or preserving session state across domains. This Skill automates importing cookies from a real Chromium browser into a headless browse session so tests can run with an authenticated context.

Core Features & Use Cases

  • Interactive picker UI to select which cookie domains to import.
  • Decrypt and load cookies into the headless browser session (Playwright) for seamless testing.
  • Ideal for QA workflows that require login flows and cross-domain testing.

Quick Start

Run the skill and use the picker to import the domains you need, then proceed with testing.

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 for QA testing?

To import cookies into a Playwright headless session, you can use an interactive picker to select specific cookie domains from a real Chromium browser, decrypt them, and load them directly into your test context to bypass manual login.

What is the best way to test authenticated pages across multiple domains without logging in manually?

The best way to test authenticated pages across multiple domains is to import real browser cookies into your headless session. This simulates a logged-in user context, allowing your QA tests to proceed seamlessly without manual login flows.

Can I select which specific cookies to import for cross-domain testing?

Yes, you can select which specific cookies to import using an interactive picker UI. This allows you to target only the necessary cookie domains required for your cross-domain QA testing workflows.

Does this cookie import approach work with Chromium browsers for headless testing?

Yes, this approach works specifically with real Chromium browsers. It decrypts the cookies stored in your local Chromium profile and loads them into the Playwright headless browser session to enable authenticated testing.

Why do my headless browser tests fail to maintain authenticated session state across domains?

Headless browser tests often fail to maintain authenticated state because they lack existing session cookies. By decrypting and importing cookies from a real Chromium browser into the Playwright session, you can preserve login state and resolve this issue.

How to decrypt and load cookies for Playwright automated testing?

To decrypt and load cookies for Playwright automated testing, run the skill to launch an interactive picker, select the desired domains, and the tool will automatically decrypt the Chromium cookies and load them into your headless session context.