gstack-setup-browser-cookies

Import cookies from a real Chromium browser into a headless Playwright browse session.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-setup-browser-cookies-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-setup-browser-cookies
Source: https://github.com/tayiorbeii/paperclip-factory-kit-hermes/tree/main/skills/paperclip/gstack-setup-browser-cookies
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-setup-browser-cookies-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Headless browser sessions used for QA testing start without any logged-in state, so authenticated pages cannot be tested. This Skill imports cookies from your real Chromium browser into the headless browse session so you can test pages that require login. ## Core Features & Use Cases - Interactive Cookie Picker: Opens a browser-based picker UI where you select which cookie domains to import, with search and per-domain controls. - Direct Domain Import: Skip the UI by specifying a domain directly, such as importing cookies for github.com from a chosen browser. - CDP Mode Detection: Checks whether the session is already connected to your real browser via CDP and skips the import when unnecessary. - Use Case: Before running QA on an authenticated dashboard, import your logged-in session cookies, then verify the import with a summary of cookie counts per domain. ## Quick Start Ask the agent to import browser cookies so you can log in to the test site, then pick the domains you want in the picker UI that opens.

Frequently Asked Questions about gstack-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 browser session?▼

Run the cookie-import-browser command from the gstack browse binary, which detects installed Chromium browsers and opens a picker UI. Select the domains you want, and the cookies are decrypted and loaded into the Playwright session.

How do I test authenticated pages with a headless browser?▼

Import cookies from your real browser first so the headless session inherits your logged-in state. After import, run the cookies command to verify the imported domains and counts before testing.

Can I import cookies for a specific domain without the picker UI?▼

Yes, pass the domain directly to the cookie-import-browser command, for example with --domain github.com, along with the browser name. This skips the interactive picker entirely.

Does cookie import work when connected via CDP?▼

No import is needed in CDP mode because the session is already attached to your real browser, so your cookies and sessions are available directly. The skill detects this and stops early.

Why does cookie import prompt for Keychain access on macOS?▼

The first import per browser on macOS may trigger a Keychain dialog because cookie decryption requires access to the browser's stored encryption key. Click Allow or Always Allow to proceed.