setup-browser-cookies

Import cookies from Chromium-based browsers into a headless browsing session.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session to enable authenticated QA testing without manual login steps.

Core Features & Use Cases

  • Interactive cookie picker: select domains to import and apply them to the headless session.
  • Browser support: works with multiple Chromium-based browsers (Comet, Chrome, Arc, Brave, Edge).
  • Secure handling: decrypts cookies locally and loads them into the headless session without exposing values.

Quick Start

Run the one-time setup to build the cookie picker and then import desired domains using the picker.

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

To import browser cookies into a headless session, you use an interactive domain-picker to select and apply cookies from your real browser. This enables authenticated QA testing without manual login steps.

What browsers can I import cookies from for headless browsing?

You can import cookies from multiple Chromium-based browsers, specifically Comet, Chrome, Arc, Brave, and Edge. The cookie picker decrypts and loads these locally without exposing the values.

Do I need a local gstack workflow to set up the cookie picker?

Yes, you need a local gstack workflow with a browser-detection binary. You must run a one-time setup step to build the interactive picker before you can import desired domains.

Why are my headless browsing tests failing authentication?

Headless browsing tests fail authentication because they lack existing login sessions. Importing cookies from a real browser into the headless session resolves this by securely decrypting and applying them locally.