mzstack

Name: mzstack
Availability: InStock
Author: Ulanxx

Drive a persistent headless browser daemon for QA and UX testing.

Updated Mar 25, 2026

Search Tags:#automation #screenshots #qa #cli #diff #playwright #browser

Ready to run

npx skills add https://github.com/Ulanxx/mzstack --skill mzstack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mzstack
Source: https://github.com/Ulanxx/mzstack/tree/main
Command: npx skills add https://github.com/Ulanxx/mzstack --skill mzstack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, diff, and includes scripts (resource) components.

What problem does it solve?

mzstack provides Claude Code with a persistent, headless browser daemon to QA test websites, capture evidence, and accelerate workflows.

Core Features & Use Cases

Navigate pages, read content, run tests, take annotated screenshots, diff before/after, and test responsive layouts.
Supports multiple workspaces with isolated browser instances, cookie persistence, and cookie import for authenticated tests.
Enables design reviews and PR ship workflows by collecting evidence and diffs.

Quick Start

Install mzstack, then run /office-hours to frame your problem and start the design-doc workflow.

Frequently Asked Questions about mzstack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate headless browser QA testing with Claude Code?▼

Headless browser QA testing is automated by using mzstack as a persistent daemon that Claude Code drives via simple commands for navigation, content extraction, and snapshot capture across isolated workspaces.

Can I take annotated screenshots and diff before/after changes locally?▼

Annotated screenshots and visual diffing are supported natively; mzstack captures snapshots with ref labeling and diffs before/after states to provide evidence for design reviews and ship validation workflows.

Does mzstack work with Playwright for UX testing and interactions?▼

Playwright serves as the underlying browser automation dependency for mzstack, enabling UX testing through scripted interactions, responsive layout checks, and content extraction within its persistent headless daemon.

How do I run authenticated tests with cookie persistence in isolated workspaces?▼

Authenticated tests use isolated workspaces in mzstack that persist cookies and tabs per environment, while cookie import functionality allows you to inject existing sessions for secure local QA validation.

What's the best way to add telemetry and eval hooks for automated browser governance?▼

Telemetry and eval hooks for automated browser governance are integrated directly into mzstack, providing local server access with token auth to secure and monitor QA automation workflows.

Do I need bun to run the compiled binary for local headless testing?▼

Bun is required to run mzstack locally, as the skill compiles into a binary that executes the persistent headless browser daemon and manages local server token authentication.