setup-browser-cookies

Import Chromium browser cookies into a headless Playwright session.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mmunro3318/3d-render-pipeline --skill setup-browser-cookies-mmunro3318
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/mmunro3318/3d-render-pipeline/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/mmunro3318/3d-render-pipeline --skill setup-browser-cookies-mmunro3318

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproducing authenticated QA sessions is difficult when tests run in a headless environment. This Skill enables importing cookies from real Chromium-based browsers into a headless session so tests operate with the same login state without manual re-authentication.

Core Features & Use Cases

  • Import cookies from installed Chromium-based browsers into a headless Playwright session used for QA testing.
  • Open an interactive picker UI to select which domains to import, or specify a domain directly to import.
  • Persist cookies across commands to maintain authentication during automated test runs.

Quick Start

Import cookies from your real browser into the headless session, then continue with your QA 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 headless Playwright session?

You can import cookies from real Chromium-based browsers into a headless Playwright session by opening an interactive picker to select domains or specifying a domain directly to load the authentication state for your QA tests.

Why do my Playwright QA tests fail to authenticate in a headless environment?

Headless tests fail authentication because they lack the login state of real browsers. Importing cookies from an installed Chromium browser resolves this by injecting the existing authenticated session into the test run.

Can I select specific domains when importing cookies for QA testing?

Yes, you can select specific domains when importing cookies. The skill provides an interactive picker UI to choose which cookie domains to import, or you can specify a target domain directly to bypass the picker.

Do I need a browser binary present to use cookies in headless testing?

Yes, a browser binary must be present on the system. You also need to run a one-time setup step using the command line to build the browser configuration before using the interactive cookie picker.

What is the best way to persist authenticated sessions across Playwright commands?

The best way to persist sessions is to import real browser cookies into the headless environment. This maintains the authentication state across subsequent commands without requiring manual re-authentication during automated runs.

Do I need to install bun to use the interactive cookie picker?

Installing bun is optional but recommended. The skill provides optional guidance to install bun if needed, alongside the required one-time setup step and an existing browser binary.