setup-browser-cookies

Import browser cookies into a Playwright headless session for authenticated QA testing.

107|19|Updated Mar 23, 2026

Search Tags:#authentication #browser #headless #import #session-persistence #cookie #qa-testing

Ready to run

npx skills add https://github.com/mr-daedalium/ostack --skill setup-browser-cookies-mr-daedalium

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session to enable authenticated QA testing without manual login.

Core Features & Use Cases

Interactive cookie picker UI to select which domains to import.
Works across major browsers (Comet, Chrome, Arc, Brave, Edge) for cross-browser testing.
Maintains session state by loading cookies into the Playwright session and persisting cookies across commands.

Quick Start

Run the setup-browser-cookies skill and follow the on-screen prompts to 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 browser cookies into a headless session for QA testing?▼

You can import browser cookies into a headless session by running the setup-browser-cookies skill, which decrypts and loads cookies from your real browser to simulate an authenticated user. An interactive picker UI lets you select specific domains to load.

Can I use cookies from Chrome, Arc, Brave, and Edge for cross-browser testing?▼

Yes, cookie import works across major browsers including Chrome, Arc, Brave, Edge, and Comet. This cross-browser support allows you to load authenticated sessions from your preferred browser into the headless environment for QA testing.

How do I maintain authenticated session state across multiple headless commands?▼

To maintain session state, the skill loads cookies into the Playwright session and persists them between commands. This ensures your authenticated state remains active throughout your QA testing workflow without requiring manual re-login.

What is the best way to test authenticated pages without manually logging in?▼

The best way to test authenticated pages without manual login is to import existing browser cookies into your headless session. This simulates an authenticated user by transferring your active session tokens directly into the testing environment.

Do I need to select specific cookie domains when setting up a headless session?▼

Yes, you need to select specific cookie domains using the interactive picker UI. This allows you to choose exactly which authenticated domains are loaded into the headless session, preventing unnecessary cookies from cluttering your testing environment.