A desktop QA app that walks your sitemap, records reviewer interactions, and files GitHub issues with the evidence baked in. If your site has the GlitchReplay SDK loaded, every report auto-links to the exact session replay where the bug showed up — no extra setup.
Early access · install with git clone · macOS · Windows · Linux
Point it at sitemap.xml or seed URLs and it discovers every route — including app routes the sitemap missed. Track which pages are approved, which need rechecks, and which have open issues.
Screenshots, console errors, network failures, browser metadata, and the reviewer's clicks and form changes — all attached to the issue automatically. No more 'works on my machine.'
Hit Report. Sentinel runs gh issue create against the repo of your choice with everything pre-filled. Issues open in your repo, not in some vendor portal.
If the page has the GlitchReplay SDK, Sentinel calls into it via window.glitchreplay.reportQA() and rides the active session replay into the dashboard. Reviewer sees the bug. Engineer sees the replay.
QA progress lives in your repo. Config, screenshots, and run history sync via plain git on a per-reviewer branch. No backend, no signups, no SaaS lock-in.
Sentinel never uploads anything to a vendor. When it does file a GlitchReplay event, the customer site's existing PII rules and replay privacy level apply — strict mode masks the way it would for a real user.
Most QA tools capture screenshots. Sentinel does too — but if GlitchReplay is on the page, the replay was already recorded. Sentinel just connects the report to it.
Sentinel opens your site in a webview. The page's GlitchReplay SDK starts recording — exactly the way it does for real visitors.
Click Report Issue, type notes. Sentinel collects console errors, network failures, the click sequence — and calls into the page's SDK.
GlitchReplay creates the issue with the active replay linked. The GitHub ticket links back. One reviewer click; one engineer click to reproduce.
For the SDK side of the integration, drop @glitchreplay/qa-report into your Sentry.init integrations. That exposes window.glitchreplay.reportQA(...) for Sentinel — or any QA tool — to call into. No additional DSN, no separate auth, no replay re-upload.
No signed binaries yet — Sentinel runs from source for now. You'll need Node 20+ and the GitHub CLI (Sentinel uses gh to file issues).
git clone https://github.com/spconroy/glitchreplay-sentinel.git
cd glitchreplay-sentinel
npm install
cp config/projects.example.json config/projects.json
gh auth login # if you haven't already
npm startUpdates: git pull && npm install. Signed installers (macOS .dmg, Windows .exe, Linux .AppImage) will land once the project graduates from early access.
Sentinel works as a standalone QA tool — point it at any site, file GitHub issues, ship product. But if you've already got the GlitchReplay SDK on your site, every QA report you file will land in the same dashboard you use for production errors, with the session that triggered it attached.
That means one issues queue. QA-discovered defects, real production errors, and accessibility violations all triaged together, with replays for everything.