Today · Notifications

Notifications

Triage-first, not firehose. Alerts ranked by severity floor × 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.

Start here if you want to know what needs doing next across your repos: Today.

See it in motion

Where to find it

  • Localhost: /notifications.html?repo=<id>
  • Hosted: /team/notifications
  • Navigation: Local settings in the sidebar, then Notifications under Workspace utilities
  • Keyboard: ⌘ K then notifications
  • API: GET /api/notifications · GET and PUT /api/triage-config · POST /api/triage/test (score only, no side effects) · POST /api/triage/process (score and act)
  • Channels: desktop · Slack webhook · email

What it does for you

Alert fatigue is the failure mode, not the feature.Capped at one push per signal class per repo per day by default, tunable per rule (a per-rule dailyCap of 0 lifts the cap). Lesson coverage suppresses recurrence: if an active Lesson trigger matches the defect, the alert is silent and a prevention event is recorded instead.
Severity and confidence band decide what interrupts you.A signal scores as its severity floor times the confidence band of its causal link. A crit finding with an exact-band link pushes; the same finding with a weak link is logged and waits for you. Blast radius is in the formula, but nothing feeds the ranker a graph yet, so it adds nothing to the score today.
Per-rule channel config.A rule names the channels it may use, so critical findings can go to Slack and email while everything else stays on desktop. There is no global "alert me about everything" switch.

Configure

  • Slack webhook URL: the Channels panel on the Notifications tab, saved over PUT /api/triage-config.
  • Email: turn the channel on and set a destination address in the Channels panel; a rule's channel list then filters which of the enabled channels it uses. Sent through Resend's HTTP API with RESEND_API_KEY; without the key the send reports RESEND_API_KEY not set and nothing goes out.
  • Per-rule on/off: disable rules that don't apply to this repo.

Use it well

Tune notifications down, not up. Every channel ships off, so a fresh install pushes nothing until you turn desktop, Slack or email on. Once one is on, the default cap is one push per signal class per repo per day. If a rule fires twice without you acting on it, either fix the rule or accept the suppression.

Read more

Last updated