setup-browser-cookies

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

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill setup-browser-cookies-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/setup-browser-cookies
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill setup-browser-cookies-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Headless browser sessions start with no login state, so QA testing authenticated pages requires manually recreating sessions. This Skill imports cookies from your real Chromium browser into the headless browse session, giving you authenticated access without re-entering credentials. ## Core Features & Use Cases - Interactive Cookie Picker: Opens a picker UI in your default browser 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 (e.g., github.com) for scripted imports. - CDP Mode Detection: Detects when the browse session is already connected to your real browser via CDP and skips unnecessary imports. - Use Case: Before running QA tests against a staging site that requires login, import your session cookies so the headless browser can access authenticated pages immediately. ## Quick Start Ask the assistant to import cookies from your browser so you can test authenticated pages, then select the domains you want in the picker UI that opens.

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

Run the cookie-import-browser command from the gstack browse binary. It detects installed Chromium browsers and opens an interactive picker UI where you select which domains to import into the Playwright session.

How to test authenticated pages without logging in again?

Import cookies from your real browser into the headless session first. The browse session persists cookies between commands, so imported login state works immediately for subsequent page visits and QA tests.

Can I import cookies for a specific domain only?

Yes. Pass the domain directly, for example cookie-import-browser comet --domain github.com, to skip the picker UI and import only that domain's cookies from the specified browser.

Does cookie import work if the browser is connected via CDP?

No import is needed in CDP mode. When the browse session is already connected to your real browser via CDP, your cookies and sessions are available directly, and the skill tells you to skip the import.

Why does cookie import trigger a Keychain dialog on macOS?

The first import per browser on macOS may prompt a Keychain dialog because Chromium cookies are encrypted with a key stored in the system Keychain. Click Allow or Always Allow to let the import decrypt the cookies.