setup-browser-cookies

Import cookies from real browsers into a headless testing session.

Updated Nov 11, 2025

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

Ready to run

npx skills add https://github.com/rshelekhov/dotfiles --skill setup-browser-cookies-rshelekhov

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session used for automated QA testing, so you stay logged in without manual re-authentication.

Core Features & Use Cases

Interactive picker UI that lets you select which cookie domains to import into your headless session.
Supports multiple browsers and transfers cookies securely for immediate use in tests.
Useful for QA testing authenticated pages and end-to-end flows that require login state.

Quick Start

Tell me to import cookies from my real browser into the headless session and choose which domains to include.

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

You can import browser cookies into a headless session by transferring them from real browsers like Chrome, Arc, Brave, or Edge to preserve login state and avoid manual re-authentication during QA testing.

Can I select specific cookie domains to import for Playwright QA testing?▼

Yes, this cookie import process provides an interactive picker UI that allows you to select exactly which cookie domains are transferred into your headless session before testing authenticated pages.

Why do my headless browser tests fail to stay logged in on authenticated pages?▼

Headless sessions start without login state. Importing cookies from your real browser into the headless session preserves authentication, allowing automated end-to-end flows to bypass manual re-authentication.

Does this cookie import method work with multiple Chromium-based browsers?▼

Yes, it supports importing cookies from multiple real browsers, specifically Comet, Chrome, Arc, Brave, and Edge, securely transferring them for immediate use in your headless tests.

What is the best way to skip login steps in automated end-to-end testing?▼

The best way to skip manual login is to import existing authenticated cookies from a real browser into the headless session, maintaining the login state across QA tests without re-entering credentials.

How do I start importing cookies from the command line for interactive UI testing?▼

You initiate the import from the command line using Bash, which launches an interactive UI to choose specific domains and securely transfer cookies into the headless testing environment.