setup-browser-cookies

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

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/OmerFarukOruc/symphony-orchestrator --skill setup-browser-cookies-omerfarukoruc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/OmerFarukOruc/symphony-orchestrator/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/OmerFarukOruc/symphony-orchestrator --skill setup-browser-cookies-omerfarukoruc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) 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".

Core Features & Use Cases

  • Import cookies from common Chromium-based browsers into a headless browsing session.
  • Use an interactive picker to select domains to import, or specify a domain directly for quick imports.
  • Verify loaded cookies and reuse them across commands to speed up authenticated testing and QA automation.

Quick Start

Instruct the picker to import the desired domains, or run a direct-domain import to load cookies into the headless session before testing authenticated pages.

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

To import cookies into a headless test session, use an interactive picker to select cookie domains from your local Chromium-based browser, or specify a domain directly to load the decrypted cookies into your automated environment.

What browsers can I use to import cookies for automated QA testing?

You can import cookies from common Chromium-based browsers including Chrome, Arc, Brave, Edge, and Comet, provided their cookie store is accessible by the picker for decryption and loading into your headless session.

How do I authenticate a headless browser for testing without manual login?

You can authenticate a headless browser by reusing real-browser cookies loaded into the session before testing authenticated pages, bypassing manual login steps during QA automation workflows.

Can I select specific cookie domains to load into my headless browser?

Yes, you can use the interactive picker UI to select specific cookie domains to import, or you can run a direct-domain import to quickly load only the cookies needed for your authenticated testing.

Why do my authenticated workflows fail when switching to a headless browser?

Authenticated workflows fail in headless browsers because they lack your active login cookies. Importing real-browser cookies into the headless session maintains your authenticated state for QA testing.

Do I need a specific browser setup to decrypt and load cookies for automation?

You need a Chromium-based browser cookie store accessible by the picker, a compatible headless browser environment, and the ability to decrypt and load those cookies into your test session.