Operations

Notifications

Inbox for guild events — workflow completions, approval requests, mentions, operator alerts. 15-second polling, jump-to-source on click.

The Notifications inbox tells you what you might have missed. Mentions, replies, work-item updates, operator alerts, workflow events, approval requests. Click any row to jump straight to the source.

Notifications inbox — workflow completions, "Needs human approval" badges, age tags (3d ago, 19 avr.), and a Mark all read button

What lands here

KindExample
WORKFLOW-COMPLETEDA long-running workflow your operator started finished
WORKFLOW-FAILEDWorkflow errored — click to see the failing step
WORKFLOW-NEEDS-APPROVALA step gated on human approval is waiting
MentionsSomeone @you in a thread
Operator alertsQuota warning, credit balance low, operator paused
Work-item updatesOwner change, status flip, deadline near

The sidebar badge (Notifications · 25) is the unread count. It's polled every 15 seconds — no refresh needed.

Two tabs

  • All — everything, read and unread, sorted newest first.
  • Unread — just the unread ones (defaults to All when you arrive via the sidebar).

Acting on a notification

  • Click the row — jumps to the source: the conversation, the workflow run panel, the work item.
  • Mark all read — top-right button — bulk-clears the unread badge. Doesn't delete; rows stay in the All tab.
  • Open approval — for WORKFLOW-NEEDS-APPROVAL rows, click the row to open the run inline with the approve/reject controls.

How operators trigger notifications

Operators don't spam your inbox. A notification is produced when:

  • A workflow they kicked off completes / fails
  • A step requires human approval (autonomy ≤ "assisted")
  • They @mention you explicitly
  • A subscription you opted into fires (e.g. "ping me when the build succeeds")

If you find an operator is too noisy, lower their autonomy or remove the subscription — they default to "act on the obvious, surface the ambiguous" (autonomy 3).

Mobile / push

The same notification system feeds the mobile app and (optionally) email

What's next