setup-browser-cookies

Name: setup-browser-cookies
Availability: InStock
Author: nocnoc

Import cookies from Chromium-based browsers into headless Playwright sessions.

Updated Mar 21, 2026

Search Tags:#automation #playwright #headless #qa-testing #cookie-import #browser-cookies

Ready to run

npx skills add https://github.com/nocnocgroup/gstack --skill setup-browser-cookies-nocnocgroup

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps QA tests authenticated by importing cookies from real browsers into the headless testing session, reducing manual login steps.

Core Features & Use Cases

Cookie picker UI to select which domains to import.
Supports common Chromium-based browsers: Comet, Chrome, Arc, Brave, and Edge.
Keeps cookies persistent across commands in the headless session for seamless testing.
Use Case: When testing authenticated pages, import cookies to bypass login.

Quick Start

Run the one-time setup to build the cookie-import tool, then open the picker and import the domains you need.

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 Playwright headless session?▼

To import real browser cookies into a Playwright headless session, run the one-time setup script to build the cookie-import tool, then open the interactive picker to select and import the domains you need for authenticated QA flows.

Can I use cookies from Arc or Brave for Playwright QA testing?▼

Yes, you can use cookies from Arc or Brave for Playwright QA testing. The cookie import tool supports common Chromium-based browsers including Chrome, Comet, Arc, Brave, and Edge to enable authenticated testing.

What is the best way to bypass login steps in headless automation?▼

The best way to bypass login steps in headless automation is importing real browser cookies to keep QA tests authenticated. This reduces manual login steps by opening an interactive picker to choose specific domains for import.

Do I need to run a setup script before importing browser cookies?▼

Yes, you need to run a one-time setup script in the skill directory to build the cookie-import tool. After building, you must run a browser cookie picker server to execute the domain import workflow.

Why does my headless Playwright session lose authentication across commands?▼

Headless Playwright sessions lose authentication without imported cookies. This skill keeps cookies persistent across commands in the headless session, ensuring seamless authenticated testing without manual login steps.