Control a persistent headless Chromium daemon via a local CLI for browser testing.
npx skills add https://github.com/24601/gastack-pre-fork --skill gstack-24601
Please help me install this Agent Skill. Skill: gstack Source: https://github.com/24601/gastack-pre-fork/tree/main Command: npx skills add https://github.com/24601/gastack-pre-fork --skill gstack-24601
Many browser-driven QA and dogfooding workflows are slow, flaky, and lose session state because each tool launches a fresh browser. gstack provides a persistent headless Chromium daemon with ref-based element selection so agents and CLI workflows run sub-second commands, preserve cookies/tabs, and produce reliable evidence (annotated screenshots, diffs, logs) for testing and verification.
snapshot assigns @e/@c refs to elements so agents can click/fill without brittle CSS selectors.chain execution.connect) for live handoff, and handoff/resume to let a human solve CAPTCHAs or MFA then continue automated flows.Launch the gstack browse binary and use its $B commands (goto, snapshot, click, screenshot) to open a page, capture interactive refs, and save an annotated screenshot.
High-intent search queries and answers about installing and using this skill.
You can keep browser sessions persistent for Playwright QA automation by running a long-lived headless Chromium daemon that preserves cookies, tabs, and localStorage across sub-second CLI commands, eliminating cold starts.
Automate browser testing without brittle CSS selectors by using a snapshot command that assigns interactive refs to page elements, allowing agents to click or fill directly via stable references.
Yes, you can import real browser cookies into a headless Chromium daemon to handle QA flows and deployment verification requiring authenticated multi-step testing across staging and production-like environments.
The best way to handle CAPTCHAs during automated browser testing is using headed-mode handoff to let a human solve the challenge, then resume automated multi-step user journeys in the persistent daemon.
Capture visual regression evidence with annotated screenshots and snapshot diffs by running verification commands that output responsive screenshots, perf metrics, and console buffers from the persistent headless browser.
Yes, gstack works with Puppeteer for headless browser automation, building its persistent Chromium daemon and ref-based element selection on both Playwright and puppeteer-core dependencies.
fray-cloudControl a persistent headless Chromium daemon via CLI for browser automation.
g4rcezAutomate QA browser testing across URLs, interactions, and state assertions.
shekerkammaAutomate browser-based QA testing with persistent headless browser sessions.
abhishekdutta18Automate visual, functional, and accessibility testing of web pages.