setup-browser-cookies

To import real browser cookies for authenticated testing, you can use a Skill that decrypts cookies from your real Chromium browser and loads them directly into your headless Playwright session. This restores your logged-in state so QA can reach protected pages without manual authentication.

No, you do not need to manually log in each time for automated browser tests. By importing decrypted cookies from an existing authenticated Chromium browser session, you can bootstrap a logged-in state in the headless session and immediately access protected pages.

Importing cookies from a real Chromium session works by decrypting the stored browser cookies and injecting them into the Playwright session. An interactive UI lets you select exactly which cookie domains to import, ensuring the headless browser has the correct authenticated state for QA automation.

Yes, you can choose which cookie domains to import when setting up an authenticated browser session. An interactive domain selection UI allows you to pick the exact cookie domains to load into the headless Playwright session, preventing unnecessary cookies from being imported.

Cookie import stops early when the browser is already connected via CDP mode because the active connection implies a different session management context. The Skill detects this CDP mode and halts the cookie decryption and loading process to avoid conflicts with the existing browser state.

The best way to authenticate a headless browser session is to reuse your existing login by importing cookies from your real Chromium browser. This avoids repeated manual logins and allows automated end-to-end testing to immediately access authenticated pages.