Tab · Knowledge

Notifications

Triage-first, not firehose. Alerts ranked by causal blast radius × confidence band, suppressed when an active Lesson trigger already covers the defect, capped at one push per signal_class per repo per day. Per-rule channel config: desktop + Slack + email.

See it in motion

Where to find it

  • Localhost: /notifications.html?repo=<id>
  • API: /api/notifications · /api/triage-config · /api/triage/{test,process}
  • Channels: desktop · Slack webhook · email

What it does for you

Alert fatigue is the failure mode, not the feature.Caps locked at one push per signal class per repo per day. Lesson coverage suppresses recurrence — if you have a Lesson, the alert is silent.
Blast-radius ranking surfaces the biggest fires first.Causal blast radius × confidence band. A high-confidence finding that touches 12 downstream files outranks a low-confidence finding that touches 1.
Per-rule channel config.Critical findings to Slack + email; everything else stays on desktop. No global "alert me about everything" switch.

Configure

  • Slack webhook URL — Settings → Notifications → Slack.
  • Email — opt-in per rule; SMTP via Resend (Cloud) or your own provider (self-host).
  • Per-rule on/off — disable rules that don't apply to this repo.

Use it well

Tune notifications down, not up. The default is "loud on first ship, quiet after a week." If a rule fires twice without you acting on it, either fix the rule or accept the suppression.

Read more