browser-use-screenshot

Automated browser UI verification handles dev server detection, auto-login via a dev-login route or better-auth forms, page navigation, and saves screenshots to temp/ to streamline UI debugging and regression checks across dev server states.

Yes, the automated login mechanism handles authentication by navigating to a dev-login route or completing better-auth form submissions before capturing screenshots, eliminating manual login steps during UI verification.

Executing an automated browser screenshot workflow is the best way to perform visual regression checks, as it waits for page readiness after navigation and stores screenshots in temp/ for cross-page comparison and documentation.

Yes, the browser screenshot automation supports better-auth by automatically filling out login forms to authenticate the browser session before navigating to specified pages for UI verification and screenshot capture.

The screenshot process includes readiness waits before capturing the Nuxt UI to ensure all dynamic elements and Supabase data have fully loaded, preventing incomplete or inaccurate visual validation captures.

No, you do not need to manually start the dev server because the browser daemon automatically detects an existing Nuxt dev server or starts a new one, ensuring port discovery does not interfere with other active projects.