gstack

Automate headless browser QA testing by using a persistent Chromium daemon with Playwright APIs to script navigation, extract content, capture annotated screenshots, and manage cookies. This approach provides a long-lived browser environment for repeatable end-to-end test execution.

A persistent headless browser is a long-lived Chromium daemon that maintains state across multiple test runs. You need it for E2E testing when executing continuous QA workflows, canary monitoring, or production dogfooding that requires multi-workload isolation and session telemetry.

Capture visual diffs and evidence during browser automation by utilizing workflow commands that drive the headless browser to navigate pages, take annotated screenshots, and extract content. A reusable snapshot system using accessibility refs locates elements with stable selectors for accurate validations.

Yes, you need Bun installed to build the skill and run the browse CLI that starts the persistent Chromium daemon. This lightweight stateful server manages the Playwright APIs, cross-workspace isolation, and safe command execution required for your workflows.

Yes, you can use this headless browser for production dogfooding and canary monitoring. It supports scripted navigation, content extraction, and evidence capture across multiple workspaces, with safety hooks designed to guard against destructive actions during continuous monitoring sessions.

Use a persistent Chromium daemon instead of standard runners to achieve cross-workspace isolation, maintain session telemetry, and execute safe commands across multi-workload environments. The long-lived daemon state enables faster repetitive navigation and content extraction for continuous QA workflows.