setup-browser-cookies

Import Chromium session cookies into a headless Playwright session.

Updated Feb 24, 2026

Search Tags:#authentication #playwright #chromium #headless browser #qa testing #browser cookies #cookie import

Ready to run

npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill setup-browser-cookies-jia-hong-peng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill setup-browser-cookies-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Headless browser sessions start with a clean slate, lacking any authentication state. This Skill solves that by importing cookies from your real Chromium browser into the headless session, enabling immediate testing of pages that require login.

Core Features & Use Cases

Interactive Cookie Picker: Automatically detects installed Chromium browsers and opens a UI to select which cookie domains to import.
Direct Domain Import: Skip the UI by specifying a domain directly for quick, repeatable authentication.
QA Testing Workflow: Use before testing authenticated pages to avoid manual login steps in headless environments.
Use Case: You need to QA a staging site protected by GitHub OAuth. Instead of logging in manually through the headless browser, import your GitHub cookies and start testing instantly.

Quick Start

Use the setup-browser-cookies skill to import cookies from your browser for the current site.

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?▼

You can import browser cookies into a Playwright headless session by transferring authenticated session cookies from your local Chromium browser, enabling immediate access to pages requiring login without manual authentication steps.

Why does my headless browser session lack authentication state for QA testing?▼

Headless browser sessions lack authentication state because they start with a clean slate. Importing cookies from your real Chromium browser solves this by transferring your existing session state into the headless environment for testing.

Can I specify cookie domains directly via command line instead of using a picker UI?▼

Yes, you can specify cookie domains directly via the command line for quick, repeatable authentication imports. Alternatively, an interactive picker UI automatically detects installed Chromium browsers to select which cookie domains to import.

Does this cookie import method work with Chromium browsers only?▼

This cookie import method works with local Chromium browsers, requiring the gstack browse binary and browser cookie decryption capabilities to transfer session state into the headless Playwright session for QA testing.

What is the best way to test authenticated staging sites in a headless environment?▼

The best way to test authenticated staging sites is importing real browser cookies into the headless session. For example, import GitHub OAuth cookies to QA a protected staging site instantly without manually logging in through the headless browser.

Do I need to manually log in to test authenticated pages with Playwright?▼

No, you do not need to manually log in to test authenticated pages. By importing existing authenticated session cookies from your local Chromium browser, you can bypass manual login steps entirely in headless QA testing workflows.