setup-browser-cookies

Import Chromium browser cookies into headless Playwright or Puppeteer sessions.

Updated Apr 16, 2026

Search Tags:#automation #qa #playwright #browser #headless #cookies #chromium

Ready to run

npx skills add https://github.com/vib795/copilot-anatomy --skill setup-browser-cookies-vib795

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to streamline QA and testing without manual login steps.

Core Features & Use Cases

Interactive picker UI to select cookie domains for import
Enables authenticated QA sessions in headless browser environments
Works before QA testing to bootstrap cookies quickly

Quick Start

Import cookies from your real browser by running the skill, then use the picker to choose domains to import.

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 real browser cookies into a headless Playwright session by using a setup tool that reads cookies from your local Chromium browser and injects them into the automated environment, enabling authenticated QA workflows without manual login.

Can I use my existing Chromium login cookies for automated QA testing?▼

Yes, you can use existing Chromium login cookies for automated QA testing. The setup process reads persistent login cookies from your real browser profile and replicates them in the headless session to skip manual authentication steps.

What is the best way to bootstrap authenticated headless browser tests?▼

The best way to bootstrap authenticated headless browser tests is to import cookies directly from a real Chromium browser profile. An interactive picker UI helps you select specific cookie domains to ensure deterministic session replication for your QA tests.

How do I select specific cookie domains to import for my Puppeteer tests?▼

To select specific cookie domains for Puppeteer tests, you run the cookie import setup and use the interactive picker UI. This UI guides you through choosing exact domains from your real Chromium browser to inject into the headless session.

Does importing browser cookies for headless sessions work with environment data?▼

Yes, importing browser cookies for headless sessions works with environment data. The setup process reads environment data and uses UI prompts to guide cookie selection, ensuring deterministic session replication across different testing environments.