Monitors a deployed URL after releases, checking HTTP status, console errors, performance, assets and SSE streams for regressions.
- What it does
- Canary Watch performs post-deploy verification of a deployed URL, running a single pass or a sustained loop over a set window. It checks HTTP status, new console errors, network and API failures, performance metrics such as LCP and CLS against a baseline, key page content, static asset responses, and SSE stream connectivity. It applies critical, warning and info thresholds and produces a markdown canary report with status, baseline comparisons and deltas, optionally notifying via desktop or Slack/Discord webhook and logging to a local file.
- When to use it
- Use it after deploying to production or staging, after merging a risky pull request, after dependency upgrades, or during a launch window. It is also suited to confirming that a fix actually resolved the issue and to comparing staging against production.
- Requirements
- Instructions only; no scripts are shipped. It expects a deployed URL to monitor and, for regression comparisons, baseline values. Optional Slack or Discord webhook for notifications, desktop notification support, and write access to a local log path. Network access to the monitored site is required.
Canary Watch — Post-Deploy Monitoring
When to Use
- After deploying to production or staging
- After merging a risky PR
- When you want to verify a fix actually fixed it
- Continuous monitoring during a launch window
- After dependency upgrades
How It Works
Monitors a deployed URL for regressions. Runs in a loop until stopped or until the watch window expires.
What It Watches
Watch Modes
Quick check (default): single pass, report results
Sustained watch: check every N minutes for M hours
Diff mode: compare staging vs production
Alert Thresholds
Notifications
When a critical threshold is crossed:
- Desktop notification (macOS/Linux)
- Optional: Slack/Discord webhook
- Log to
~/.claude/canary-watch.log
Output
Integration
Pair with:
/browser-qa for pre-deploy verification- Hooks: add as a PostToolUse hook on
git push to auto-check after deploys
- CI: run in GitHub Actions after deploy step
