What problem does it solve? Browser automation scripts typically lose page state between executions, forcing you to re-navigate and re-authenticate on every run. This Skill runs a persistent browser server so pages, cookies, and sessions survive across multiple script executions. ## Core Features & Use Cases - Persistent Named Pages: Create named pages (e.g., "checkout", "login") that stay alive on the server between script runs, preserving cookies and session state. - Two Operation Modes: Launch a fresh headless Chromium instance, or connect to the user's real Chrome browser via an extension relay to act on already-authenticated sessions. - AI-Friendly Element Discovery: Use ARIA snapshots with element refs to find and interact with buttons, links, and forms without writing selectors blind. - Use Case: Scrape a paginated dashboard behind a login by connecting to your existing Chrome session, navigating pages incrementally, and capturing screenshots or network data at each step. ## Quick Start Start the dev-browser server and navigate to a website, then take a screenshot of the page.