skills.rest
timurgaleev
timurgaleevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

connect-chrome

Import Chrome session cookies into the browse daemon for authenticated browsing.

5|Updated Apr 24, 2026
Search Tags:#automation#testing#authentication#chrome#cookies#browse-daemon
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill connect-chrome-timurgaleev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: connect-chrome
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/connect-chrome
Command: npx skills add https://github.com/timurgaleev/vibestack --skill connect-chrome-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reuse your real Chrome cookies in the browse daemon, so authenticated pages work without re-logging-in.

Core Features & Use Cases

  • Reuse Chrome cookies in the browse daemon to maintain an authenticated session during automated browsing.
  • Avoid repeated login prompts when testing pages behind a login in local development and QA.
  • Safe cookie handling: cookies stay within the daemon session and are not written to the repo or logs.

Quick Start

Launch Chrome with remote-debugging-port, start the browse daemon, and import cookies from your Chrome session.

Frequently Asked Questions about connect-chrome

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reuse Chrome session cookies in an automated browsing daemon?▼

To reuse Chrome session cookies in an automated browsing daemon, launch Chrome with remote debugging enabled, start the daemon, and import your active cookies. This allows authenticated browsing tasks to persist sessions without manual credential entry.

What is the best way to test authenticated pages in CI without re-logging in?▼

Testing authenticated pages in CI without re-logging in is achieved by importing Chrome session cookies into the browse daemon. This enables sign-in persistence across local development, CI, and QA environments by reusing your existing authenticated session.

Does reusing Chrome cookies for automated browsing write sensitive data to disk?▼

Reusing Chrome cookies for automated browsing does not write sensitive data to disk. Safe cookie handling ensures cookies stay within the daemon session and are never written to the repository or logs during testing.

Can I use Chrome remote debugging to authenticate automated browsing tasks?▼

Yes, you can authenticate automated browsing tasks by launching Chrome with the remote-debugging-port flag enabled. Accessing the debugging port allows the browse daemon to properly import your active session cookies for automated testing.

Why does my automated browsing daemon lose the authenticated session during QA testing?▼

Automated browsing daemons lose authenticated sessions during QA testing if they lack valid session cookies. Importing your active Chrome cookies into the daemon ensures sign-in persistence and avoids repeated login prompts across testing environments.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
434

browser-debug-setup

Set up a persistent Chrome debugging environment with a dedicated profile.

Official
Intermediate
SeaLion-hubSeaLion-hub

setup-browser-cookies

Import Chromium browser cookies into headless sessions for authenticated QA testing.

Community
Intermediate
uzumaki-incuzumaki-inc

benchmark

Detect page load performance regressions via baseline comparison in PR workflows.

Official
Advanced
garrytangarrytan
127.1k

setup-browser-cookies

Import browser cookies into a headless session for authenticated web testing.

Community
Intermediate