What problem does it solve?
After a deployment, teams often miss subtle performance degradations, console errors, or HTTP failures because they lack automated monitoring that compares current metrics against a known good baseline.
Core Features & Use Cases
- Baseline Capture – Store a reference snapshot of Web Vitals, console messages, and HTTP error statistics for a given project.
- Regression Detection – Compare live metrics with the stored baseline and issue tiered alerts (CRITICAL, HIGH, MEDIUM, LOW) only when regressions persist.
- Continuous Monitoring – Optional Cron‑based polling every 60 seconds for up to 7 days, automatically re‑running the check.
- Fallback Handling – Guides for unauthenticated Vercel or disconnected browser‑devtools MCP, and optional Supabase log integration.
- Use Cases – Detect performance regressions after a Vercel production release, monitor error spikes in critical micro‑services, or verify that new UI changes don’t introduce console errors.
Quick Start
Execute /canary https://my-app.vercel.app --baseline to store a baseline, then run /canary https://my-app.vercel.app to compare and receive regression alerts.