setup-browser-cookies

Import selected cookie domains from Chromium into a headless Playwright session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to preserve authenticated state during automated tests and scripted sessions.

Core Features & Use Cases

  • Interactive cookie picker UI to choose which cookie domains to import, ensuring you control what data is loaded.
  • Decrypts and loads selected cookies into your Playwright (or headless) session so tests can run against authenticated pages without manual login.
  • Use before QA testing or automated workflows when you need a consistent logged-in state across runs.

Quick Start

Run the cookie import process to load your browser cookies 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 load real browser cookies into a headless Playwright session?

You can load real browser cookies into a headless Playwright session by using an interactive picker UI to select specific cookie domains, which are then decrypted and imported to preserve your authenticated state for automated tests.

Why do my Playwright automated tests fail on authenticated pages?

Automated tests fail on authenticated pages when session cookies are missing. You can resolve this by importing real Chromium browser cookies into the headless session to restore the logged-in state before running your QA workflows.

Can I choose which cookie domains to import into my headless browser tests?

Yes, an interactive cookie picker UI allows you to choose exactly which cookie domains to import into your headless browser tests, ensuring you maintain strict control over what data is loaded into the automation environment.

Does importing browser cookies into Playwright require a CDP-enabled browser?

Yes, importing browser cookies into Playwright requires a CDP-enabled Chromium browser to extract the real session data, and a one-time local setup to build the browser integration if needed.

What is the best way to test authenticated pages without manual login in automation?

The best way to test authenticated pages without manual login is to decrypt and load existing cookies from your real Chromium browser directly into the headless Playwright session before executing the QA testing workflow.

Are there limitations when using imported cookies for QA testing?

Limitations include potential session expiration if the original cookies become invalid and the requirement of a one-time local setup to build the browser integration for the CDP-enabled browser.