setup-browser-cookies

Import selected domain cookies from Chromium into Playwright headless sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages. Use when asked to "import cookies", "login to the site", or "authenticate the browser". (gstack)

Core Features & Use Cases

  • Import cookies from a real Chromium browser into a headless browse session.
  • Open an interactive picker UI to select domain cookies to import.
  • Use before QA testing authenticated pages to ensure session continuity.
  • Reuse imported cookies across Playwright-based tests for faster auth.

Quick Start

Open the cookie picker, select domains to import, and tell me when you're done.

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 real browser cookies into a Playwright headless session?

You import real browser cookies into a headless session by opening an interactive picker UI, selecting the desired cookie domains from your Chromium browser, and securely loading them into the Playwright workflow.

Can I reuse authenticated browser sessions for QA testing without logging in manually?

Yes, you can reuse authenticated sessions for QA testing by importing real Chromium browser cookies into the headless browser, ensuring session continuity and faster test execution across Playwright workflows.

Do I need a specific environment to import cookies for headless browser automation?

Yes, importing cookies for headless browser automation requires a gstack environment to securely handle cookie data and manage the interactive domain selection UI during Playwright workflows.

What is the best way to authenticate a headless browser for testing specific domains?

The best way to authenticate a headless browser for specific domains is to import cookies from a real Chromium browser using an interactive picker UI, securely transferring session data to the Playwright test environment.

Why does my headless browser test fail to access authenticated pages?

Headless browser tests fail to access authenticated pages when session cookies are missing; resolve this by importing real Chromium browser cookies into the headless session before running Playwright QA workflows.