setup-browser-cookies

Import Chromium browser cookies into headless sessions for authenticated QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cookies from your real Chromium browser are not available in headless test sessions. This skill imports them so QA can test authenticated pages without manual login.

Core Features & Use Cases

  • Interactive picker UI to select which cookie domains to import.
  • Imports and decrypts cookies from your real browser into the headless browse session for authenticated QA.
  • Works before QA testing authenticated pages, and when told to "import cookies" or "authenticate the browser".

Quick Start

Open the cookie picker, select the domains to import, and tell me when you're done.

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 Chromium session?

To import real browser cookies into a headless Chromium session, use an interactive picker to select specific cookie domains and load them directly into your QA testing environment.

Can I use Playwright to test authenticated pages without manual login?

Yes, you can test authenticated pages in Playwright without manual login by decrypting and importing existing browser cookies into the headless session before running your QA tests.

How does an interactive cookie domain picker work for QA testing?

An interactive cookie domain picker works by listing available authenticated domains from your real browser, allowing you to select specific domains to inject into the headless session.

Do I need a specific environment to import cookies for headless browser testing?

Yes, importing cookies for headless browser testing requires a Bash-based environment and integration with the gstack workflow to execute the decrypt and import flow.

Why are my authenticated sessions not working in headless QA testing?

Authenticated sessions fail in headless QA testing because real browser cookies are not available by default, requiring an explicit import process to decrypt and load them.

What is the best way to authenticate a headless browser using existing cookies?

The best way to authenticate a headless browser using existing cookies is to run an import flow that decrypts Chromium cookie data and injects selected domains into the session.