setup-browser-cookies

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

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill setup-browser-cookies-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/setup-browser-cookies
Command: npx skills add https://github.com/adamtpang/summon.company --skill setup-browser-cookies-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

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 so authenticated pages work immediately. ## Core Features & Use Cases - Interactive cookie picker: Opens a browser-based UI where you search domains and select which cookies to import, without exposing cookie values. - Direct domain import: Import cookies for a specific domain (e.g., github.com) from a chosen browser via a single command, skipping the UI. - CDP mode detection: Detects when the session is already connected to your real browser via CDP and skips the import entirely. - Use Case: Before running QA tests against a staging site that requires login, import your existing session cookies so the headless browser is already authenticated. ## Quick Start Ask the assistant to import your browser cookies so the headless browser is logged in before testing an authenticated page.

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 a picker UI where you select which domains to import, then the cookies are decrypted and loaded into the Playwright session.

How do I log in to a test site for automated QA testing?

Import your existing browser cookies into the headless session instead of scripting a login flow. You can import a specific domain directly, for example with the --domain flag, so the session is authenticated before tests run.

Can I import cookies for just one domain instead of all of them?

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

Do I need to import cookies if my browser is connected via CDP?

No. When the browse session is connected to your real browser over CDP, your cookies and sessions are already available. The skill checks for CDP mode first and stops if no import is needed.

Why does macOS show a Keychain dialog when importing cookies?

Chromium encrypts cookies with a key stored in the macOS Keychain, so the first import per browser triggers an access prompt. Click Allow or Always Allow to let the tool decrypt the cookies.

Are my cookie values visible in the picker UI?

No. The picker only shows domain names and cookie counts. Cookie values are never displayed in the UI, and imported cookies persist in the browse session between commands.