setup-browser-cookies

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

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill setup-browser-cookies-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill setup-browser-cookies-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated QA of authenticated pages fails when the headless browser has no logged-in session. This Skill transfers cookies from your real Chromium browser into the headless browse session so tests run against pages that require login. ## Core Features & Use Cases - Interactive cookie picker: Opens a browser-based UI to 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 with a single command, skipping the picker. - 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 on an authenticated dashboard, import your logged-in session cookies so the headless browser can access protected pages immediately. ## Quick Start Ask the assistant to import your browser cookies so the headless browser 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 for testing?

Run the cookie-import-browser command from the gstack browse binary. It detects installed Chromium browsers and opens a picker UI where you select domains to import; cookies are decrypted and loaded into the Playwright session.

How do I test authenticated pages with Playwright?

Import your logged-in session cookies from your real browser into the headless session first. Once imported, the browse session persists cookies between commands, so authenticated pages work immediately in subsequent tests.

Can I import cookies for just one domain without the picker UI?

Yes. Pass the domain directly, for example cookie-import-browser comet --domain github.com, replacing the browser name as needed. 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 it is active.

Why does cookie import trigger a Keychain dialog on macOS?

Chromium encrypts cookies with a key stored in the macOS Keychain, so the first import per browser prompts for access. Click Allow or Always Allow; on Linux, v11 cookies similarly require secret-tool or libsecret access.