dev-browser

You preserve page state across runs by launching a local server and writing small, focused scripts that reuse named pages. This approach maintains session continuity for navigating websites, filling forms, and scraping data without resetting the browser context.

ARIA snapshots provide stable element references for web automation by capturing the accessibility tree. This allows scripts to reliably locate and interact with elements across sessions, ensuring recurring browser workflows remain stable even when underlying page structures shift.

Yes, you can run browser automation in both standalone and extension modes. This dual support allows you to automate real-user workflows directly via a local server or integrate the automation capabilities into existing extension environments.

The best way to automate recurring workflows like form filling is using small, focused scripts that each perform a single action. Combined with a local server and named pages, this approach reliably automates repeated navigation and data entry tasks while preserving state.

Yes, a local server is required to run stateful browser automation scripts. The server manages the browser environment and named pages, enabling small control scripts to execute actions like taking screenshots and testing web apps while maintaining persistent state.