setup-browser-cookies

Import authenticated Chromium session cookies into headless Playwright sessions.

Updated May 27, 2026

Search Tags:#authentication #playwright #chromium #headless browser #qa testing #browser cookies #session import

Ready to run

npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill setup-browser-cookies-shmurdoc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-setup-browser-cookies
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill setup-browser-cookies-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing authenticated pages requires logged-in browser sessions, but headless browse sessions start fresh without cookies or existing login state. Manually logging in for every test run wastes time and introduces flakiness.

Core Features & Use Cases

Cookie Import: Automatically decrypts and imports cookies from installed Chromium browsers into the headless Playwright session.
Interactive Domain Picker: Opens a UI to select which cookie domains to import, giving precise control over which sessions sync.
Use Case: Before running QA tests against a staging environment, use this skill to import your admin or user session cookies so automated tests execute as an authenticated user.

Quick Start

Use the setup-browser-cookies skill to import cookies from your default browser into the current headless browse session.

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 headless Playwright session for QA testing?▼

You can import real browser cookies into a headless Playwright session by using a tool that decrypts and loads authenticated session cookies from installed Chromium browsers. This process requires interactive domain selection to specify which cookie sessions to sync for your QA tests.

Why does my headless browser start without login state during automated testing?▼

Headless browser sessions start fresh without cookies, meaning they lack the login state of your installed browsers. To resolve this, you need to import authenticated session cookies from your local Chromium browser into the headless session before executing QA tests.

What is the best way to test authenticated pages in a headless browser without manual login?▼

The best way to test authenticated pages without manual login is importing existing browser cookies into the headless session. This approach decrypts your local Chromium cookie store and applies it to Playwright, bypassing repetitive logins and reducing test flakiness.

Can I select specific cookie domains to import into my Playwright test session?▼

Yes, you can select specific cookie domains to import into your Playwright test session. The cookie import process features an interactive domain picker UI, giving you precise control over which authenticated sessions are synced to the headless browser.

Do I need a specific binary to decrypt Chromium cookies for headless testing?▼

Yes, you need the gstack browse binary to decrypt Chromium cookies for headless testing. This binary handles the decryption and loading of the browser cookie stores, enabling the transfer of authenticated sessions into the Playwright environment.

What are the limitations of using imported browser cookies for QA testing?▼

Limitations of using imported browser cookies include dependency on the gstack browse binary and local Chromium browser installations. Additionally, imported sessions may expire or invalidate if the original browser logs out, potentially causing headless QA tests to fail unexpectedly.