setup-browser-cookies

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

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill setup-browser-cookies-raghavbadhwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/raghavbadhwar/rstack/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill setup-browser-cookies-raghavbadhwar

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 authenticated pages without re-entering credentials. ## Core Features & Use Cases - Interactive cookie picker: Runs cookie-import-browser to detect installed Chromium browsers and open a picker UI where you search domains and select which cookies to import. - Direct domain import: Import cookies for a specific domain non-interactively, e.g. cookie-import-browser comet --domain github.com. - CDP mode detection: Skips the import entirely when the browse session is already connected to your real browser via CDP, since cookies are already available. - Use Case: Before running QA on an authenticated dashboard, import your logged-in session cookies, then verify with $B cookies to see per-domain cookie counts. ## Quick Start Ask the agent to import cookies from your browser so you can log in to the test site, then pick the domains 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 search domains and click to import their cookies into the Playwright session.

How do I test authenticated pages with a headless browser?

Import cookies from your real logged-in browser first, then the headless session reuses that authenticated state. Verify the import with the cookies command, which shows per-domain cookie counts.

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

Yes. Pass the browser name and domain directly, for example cookie-import-browser comet --domain github.com. This skips the interactive picker and imports only that domain's cookies.

Do I need to import cookies when using CDP mode?

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

Why does cookie import trigger a Keychain dialog on macOS?

Chromium encrypts cookies using the macOS Keychain, so the first import per browser prompts for access. Click Allow or Always Allow to let the tool decrypt the cookies.

Are cookie values exposed in the picker UI?

No. The picker UI only shows domain names and cookie counts. Cookie values are decrypted and loaded into the session without being displayed.