setup-browser-cookies

Import Chromium browser cookies into a headless session with domain selection.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill setup-browser-cookies-vertakhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill setup-browser-cookies-vertakhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deployed QA and automation tests often fail because the browser session is not authenticated. This skill imports cookies from your real Chromium browser into the headless browse session so tests can run with a valid logged-in state.

Core Features & Use Cases

  • Interactive picker UI to select which cookie domains to import into the headless session.
  • CDP-mode check to avoid unnecessary imports when your browser is already connected.
  • Session persistence and repeatable setup for authenticated QA tests across runs.

Quick Start

Run the setup-browser-cookies skill to import cookies from your Chromium browser into the headless browse session.

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 cookies from my real browser into a headless browser session?

You can import cookies from a real Chromium browser into a headless session by using an interactive domain picker to select specific authenticated cookie domains, enabling automated QA tests to run with a valid logged-in state.

Why do my authenticated QA tests fail in a headless browser?

Authenticated QA tests fail in a headless browser because the session lacks valid login cookies. Importing cookies from your real Chromium browser resolves this by providing the required authenticated state for testing protected pages.

Can I select specific cookie domains to import for automated browser workflows?

Yes, you can select specific cookie domains to import using an interactive picker UI. This ensures only the necessary authenticated domains are loaded into the headless browser session for your automated workflows.

Does importing cookies work if my browser is already connected via CDP?

If your browser is already connected via CDP, the skill performs a CDP-mode check to avoid unnecessary cookie imports. This prevents redundant operations when the authenticated session is already active.

How do I persist authenticated sessions across multiple QA test runs?

You can persist authenticated sessions across multiple QA test runs by importing cookies into the headless browser. This provides session persistence and repeatable setup for authenticated workflows across repeated executions.

Do I need a specific browser type to import cookies into automated tests?

You need a Chromium-based browser to import cookies into automated tests. The skill extracts cookies from your local Chromium browser profile and applies them to the headless browser session for QA testing.