setup-browser-cookies

Name: setup-browser-cookies
Availability: InStock
Author: cegit27

Import authenticated Chromium session cookies into a headless browser session.

3|14|Updated Mar 10, 2026

Search Tags:#browser automation #authenticated sessions #headless testing #chromium #qa testing #cookie import

Ready to run

npx skills add https://github.com/cegit27/moodle-proctor --skill setup-browser-cookies-cegit27

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill setup-browser-cookies-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Headless browser sessions lack the authenticated cookies from your local Chromium browser, making it impossible to test login-protected pages or replicate real user sessions without manual re-authentication for every test run.

Core Features & Use Cases

Interactive Cookie Picker: Auto-detects installed Chromium browsers and opens a UI to select which cookie domains to import, with no exposure of raw cookie values.
Direct Domain Import: Skip the picker UI and import cookies for a specific domain in a single step for fast, repeatable workflows.
Use Case: QA testers and developers can instantly load their existing site sessions into headless browsers to test authenticated features, debug login flows, or review user-specific content without manual credential entry.

Quick Start

Use the setup-browser-cookies skill to import your logged-in session cookies for your team's internal project management tool into the current headless browser to test authenticated admin features.

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 authenticated browser cookies into a headless testing session?▼

To import authenticated browser cookies into a headless testing session, you use a tool that extracts session data from your local Chromium browser and loads it directly, bypassing manual login steps for protected pages.

Can I use my local Chromium browser session for QA testing without re-entering credentials?▼

Yes, you can use your local Chromium browser session for QA testing by importing the existing authenticated cookies into the headless browser, allowing you to test login-protected features and user-specific content without re-entering credentials.

What is the best way to skip manual login when running headless browser automation?▼

The best way to skip manual login during headless browser automation is to import real session cookies from your local browser via an interactive picker UI or direct domain specification, instantly granting the headless session access to authenticated areas.

Do I need a specific browser installation to import session cookies for automated testing?▼

Yes, you need a compatible Chromium browser installation and the gstack browse binary to detect your browser and extract the session cookies required for automated testing workflows.

How does the interactive cookie picker protect my session data during import?▼

The interactive cookie picker protects your session data by allowing you to select which cookie domains to import through a UI that provides no exposure of the raw cookie values during the headless browser setup process.

Can I target a specific domain to import cookies for repeatable headless testing workflows?▼

Yes, you can target a specific domain to import cookies for repeatable headless testing workflows by using direct domain import, which skips the interactive picker UI and loads the required session in a single step.