setup-browser-cookies

Import cookies from local Chromium browsers into headless browsing sessions.

Updated Mar 27, 2026

Search Tags:#automation #testing #session #browser #headless #cookies #chromium

Ready to run

npx skills add https://github.com/BaGyun0107/harness-starterkit --skill setup-browser-cookies-bagyun0107

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/BaGyun0107/harness-starterkit/tree/main/.agents/skills/gstack-setup-browser-cookies
Command: npx skills add https://github.com/BaGyun0107/harness-starterkit --skill setup-browser-cookies-bagyun0107

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill allows you to import cookies from your real Chromium browser into a headless browsing session, enabling authenticated and personalized testing environments.

Core Features & Use Cases

Cookie Import: Fetch cookies from a local Chromium browser to replicate logged-in sessions.
Browser Compatibility: Supports connecting to various installed browsers across platforms.
Use Case: Log into a website once in your browser, then import cookies to run headless tests on the same session without login prompts.

Quick Start

Use the gstack-setup-browser-cookies skill to import cookies from Chrome into your headless browsing 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 browser cookies into a headless session for automated testing?▼

To import browser cookies into a headless session, fetch them from your local Chromium browser to replicate logged-in states. This seamlessly transfers your active login data into automated workflows without requiring fresh authentication prompts.

Why does my headless browser testing fail with login prompts after authentication?▼

Headless browser testing triggers login prompts because automated sessions do not share your real browser's authentication state by default. Importing cookies from a local Chromium browser resolves this by replicating the logged-in session for your tests.

Can I use my existing Chromium browser session for headless automation workflows?▼

Yes, you can use your existing Chromium browser session for headless automation workflows. The process fetches cookies from your installed local browser, ensuring seamless transfer of login sessions and personalized data into the automated environment.

What is the best way to run authenticated tests in a headless browser environment?▼

The best way to run authenticated tests in a headless browser environment is importing cookies from a real Chromium browser. This approach bypasses repeated logins by directly transferring your active session data into the headless testing setup.

Does importing cookies for headless testing work across different installed browsers?▼

Yes, importing cookies for headless testing works across different installed browsers. The functionality supports connecting to various installed Chromium browsers across platforms, ensuring compatibility for your local browser setup and automated workflows.