canary

Post-deploy monitoring captures console errors, performance regressions, and page failures by running an automated canary check against your targeted live URLs. It uses a browse daemon to capture screenshots and metrics, comparing live behavior against stored baselines to detect silent user experience degradation.

A canary check is a post-deploy verification process that monitors a live application to detect console errors and performance regressions. It captures baselines, screenshots, and metrics across targeted pages, alerting you when anomalies are detected so you can rapidly rollback or investigate.

Run /canary <url> to start a 10-minute post-deploy canary monitor. You can optionally customize the duration, page selection, baseline capture, and specific checks to target the exact pages you need to verify for production health.

Yes, production health checks support baseline capture and comparison using automated screenshots, console logs, and performance data. The browse daemon stores these baselines and alerts you when live application behavior deviates from the established metrics.

Yes, the canary monitoring skill operates without external dependencies. It leverages an internal browse daemon to directly capture screenshots, console errors, and performance data across your targeted pages during the post-deploy verification window.

Automated screenshot capture during post-deploy verification ensures new changes do not silently degrade the user experience. By comparing live screenshots against established baselines, you can visually detect page failures and performance regressions that require immediate investigation or rollback.