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 and reuse named pages (e.g., "login", "checkout") that stay alive on the server between script runs. - Two Operation Modes: Launch a fresh standalone Chromium instance, or connect to the user's real Chrome browser via an extension relay for authenticated sessions. - AI-Friendly Element Discovery: Use ARIA snapshots with element refs to find and interact with page elements without writing selectors blind. - Use Case: Log into a web app once, then run a series of small scripts to fill a form, take a screenshot, and scrape paginated API data — all without losing your session. ## Quick Start Start the dev-browser server and navigate to https://example.com, then take a screenshot of the homepage.