setup-browser-cookies

Import authenticated Chromium session cookies into a headless Playwright environment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authenticated web applications block headless browsers from accessing protected content, requiring manual cookie export and import workflows that break easily.

Core Features & Use Cases

  • Browser Cookie Import: Automatically decrypts and imports cookies from installed Chromium browsers into the headless Playwright session.
  • Interactive Domain Picker: Opens a visual UI to select which cookie domains to import, supporting multi-browser workflows.
  • Use Case: When running QA tests on a staging site that requires GitHub login, use this Skill to import your GitHub cookies so the headless browser can access dashboard pages without re-authenticating.

Quick Start

Use the setup-browser-cookies skill to import your logged-in browser sessions into the headless browse session for authenticated testing.

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 browser cookies into Playwright, this Skill decrypts and transfers authenticated session cookies from your local Chromium browser directly into the headless browsing environment for testing.

Can I use my existing logged-in session for QA testing instead of re-authenticating?

Yes, you can use your existing logged-in session for QA testing by importing cookies from your local Chromium browser, bypassing manual login workflows and single sign-on prompts in the headless environment.

What do I need to decrypt Chromium cookies for automated browser testing?

To decrypt Chromium cookies for automated browser testing, you need the gstack browse binary and access to your system's Chromium cookie storage to successfully transfer sessions into Playwright.

How does cookie import handle multiple domains for authenticated web scraping?

For authenticated web scraping, the cookie import process opens an interactive domain picker UI, allowing you to visually select which specific cookie domains to import into the headless Playwright session.

Is manual cookie export required for Playwright single sign-on workflows?

No, manual cookie export is not required for Playwright single sign-on workflows; this Skill automatically decrypts and imports the necessary authenticated session cookies from your installed Chromium browser.

Why do headless browsers fail to access protected pages during QA testing?

Headless browsers fail to access protected pages during QA testing because they lack authenticated session cookies, a problem solved by importing decrypted cookies from your local Chromium browser.