browse-use

Persistent browser sessions are maintained using Playwright-based daemon sessions with storage-backed auth state. This enables auth inheritance and session isolation, allowing subsequent web scraping or form filling tasks to reuse existing login credentials without re-authenticating.

Auth snapshot inheritance in browser automation allows stored authentication state to be passed across multiple sessions. This tool uses storage-backed auth state to isolate named sessions, preventing repeated logins during automated testing or web scraping across different sites.

Yes, headless browser automation supports CDP-based debugging options. While it operates headless by default to streamline web automation workflows, you can switch to optional headed mode for debugging or utilize CDP endpoints for deeper inspection.

Yes, you can run multiple named sessions for isolated automated testing. The tool satisfies requirements for named sessions and session isolation via Playwright-based daemon sessions, ensuring separate auth states and storage contexts for concurrent tasks.

To execute a custom browser task script, write your JavaScript logic to a file like /tmp/browse-task.js, then run it using the tool's execution command. This invokes the Playwright-based daemon to process web scraping or screenshotting tasks with active persistent sessions.

Daemon sessions provide auth inheritance and persistent sessions that standard browser automation scripts lack. By maintaining storage-backed auth state, they eliminate redundant logins and streamline workflows across multiple sites, which is critical for efficient web scraping and automated testing.