skills.rest
ibalasite
ibalasiteCOMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import cookies from a local Chromium browser into a headless session.

Updated Mar 29, 2026
Search Tags:#testing#authentication#playwright#browser#cookies#chromium
One-click install
npx skills add https://github.com/ibalasite/gstack --skill setup-browser-cookies-ibalasite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/ibalasite/gstack/tree/main/setup-browser-cookies
Command: npx skills add https://github.com/ibalasite/gstack --skill setup-browser-cookies-ibalasite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Headless browser sessions often lack the authenticated cookies from a user's real browser, making QA and testing of logged-in pages difficult or impossible without manual re-login. This Skill imports cookies from an installed Chromium browser into the headless browse session so authenticated pages work immediately.

Core Features & Use Cases

  • Interactive cookie picker: Opens a browser-based UI to select which domains' cookies to import.
  • Direct domain import: Accepts a domain argument to skip the UI for scripted workflows.
  • Environment-aware handling: Notes macOS Keychain prompts and Linux libsecret requirements, and verifies imported cookie counts.
  • Use Case: Authenticate a headless Playwright QA run by importing your existing GitHub or internal SSO cookies so tests can run against authenticated pages.

Quick Start

Run the setup-browser-cookies skill, use the browser picker to choose domains to import, then confirm 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 headless Playwright session?▼

You can import real browser cookies into a headless session by using an interactive domain picker or a direct domain argument to transfer login states from a local Chromium browser into automated Playwright tests.

Why do my automated QA tests fail on authenticated pages in headless browsers?▼

Automated QA tests fail because headless browser sessions lack the authenticated cookies from your real browser. Importing cookies from a local Chromium installation resolves this by enabling immediate access to logged-in pages without manual re-login.

Can I script cookie imports for automated testing without a browser UI?▼

Yes, you can script cookie imports by providing a direct domain argument. This skips the interactive browser UI picker, enabling seamless integration into automated Playwright workflows and scripted testing pipelines.

Do I need macOS Keychain access to use Chromium cookies for testing?▼

Yes, accessing Chromium cookies requires unlocking browser-protected storage like macOS Keychain or Linux libsecret. The cookie import process needs this access to decrypt, verify, and transfer authenticated login sessions into headless testing.

What is the best way to test authenticated pages with a headless browser?▼

The best way to test authenticated pages with a headless browser is importing existing login cookies from a local Chromium installation. This bypasses manual re-login during QA by directly applying your active session cookies to the headless environment.

Related Skills

Explore More Software Engineering Skills→
VanLVanL
1

setup-browser-cookies

Import decrypted Chromium cookies into a headless Playwright session.

Community
Intermediate
wormholecowboywormholecowboy
1

agent-browser

Automate browser tasks via CLI with headless Chromium.

Community
Intermediate
wodehwodeh

setup-browser-cookies

Import decrypted Chromium cookies into a Playwright headless session.

Community
Advanced
kk20300113-pngkk20300113-png

setup-browser-cookies

Import decrypted Chromium session cookies into Playwright headless browser sessions.

Community
Intermediate