**For engineering** # A check on the PR for the flows customers are taught. Walkthroughs are YAML next to the code and run like tests. A failure is filed with the video, an intended change is one approval, and you never maintain a help center. ## In the repo, reviewed like code A walkthrough names the feature it covers and the source files it anchors to. Record it on your laptop against localhost with `npx stagewright record`, or have your coding agent write it through the MCP server. \[Illustration\] A walkthrough file, .walkthroughs/invite-teammate.yaml: an id, the feature it covers, the source files it anchors to, and steps that each have narration, actions and an expect check. ## A verdict people trust Every failure is recorded twice before it's judged, so the check fails only on a regression or a walkthrough your change broke. Flaky runs are reported, never blocking. Only walkthroughs your changed files can affect are recorded. - The GitHub App, or `stagewright ci` in GitHub Actions, GitLab, Azure DevOps and Bitbucket. - Exit code 1 is the only one that should block a merge. \[Illustration\] How a pull request is judged: Unchanged passes. UI changed or new waits for approval. A failure that repeats where the PR touched the walkthrough's anchors asks for the walkthrough to be updated; one that repeats where it didn't is a regression, filed as an issue. A failure that doesn't repeat is flaky and never blocks. Walkthroughs the change can't affect are skipped. ## Found, filed, fixed, proven A regression lands in Linear, Jira or GitHub Issues with the clip of the failing step, the failing selector, the second run's result and a trace, assigned to the PR's author. Hand it to a coding agent with `/stagewright:fix`. When the fix PR says `Fixes ACM-231`, the walkthrough is replayed and the verdict goes back on the PR and the issue. \[Illustration\] Issue ACM-231 in Linear, filed by Stagewright: “Invite a teammate: Send invite button not found”. It carries the clip of the failing step at 0:58, numbered steps to reproduce, the failing check, the result of the automatic second run, the PR author as assignee, and how to hand the fix to a coding agent. Its activity ends with “Fix proven on PR #418 at 3f9a2c1”. ## Try it on your own product Record a first walkthrough on your machine with no account. PR checks, approvals and publishing are in private beta: join the waitlist and we'll set you up by hand. npx stagewright init [Join the waitlist](https://app.stagewright.ai/?waitlist)[Developer docs](https://stagewright.ai/developers)