Notices

Member·3 minutes to read

What this does for you

The bell in the conversation header holds every notice you have not cleared, so nothing important is lost even when you miss the moment it happened.

Before you start

  • Nothing to set up — the bell is always in the conversation header, next to the account menu.
  • A bot's own Notifications toggle, in its settings pane, decides whether that bot writes a "finished or needs input" notice at all.

Steps

  1. Press the bell. It fetches your notices only when you open it, not on every page load, so a badge count is not kept live in the background (apps/web/components/notices/tray.tsx:40-43,66-68).

    <!-- shot: notice-inbox-01-phone.png | The notice tray, on a phone --> <!-- shot: notice-inbox-01-desktop.png | The notice tray, on a desktop -->
  2. Read a row. Each one shows the bot's avatar (or a plain ! glyph when there is none), a title, a relative time, and — on a run that failed — a request id (apps/web/components/notices/row.tsx:45-85). Pressing a row marks it read and, when it carries one, takes you to the page it names.

  3. Press Clear to remove a row from the tray. Clearing never undoes whatever the notice reported — the control reads Clear, never Undo (apps/web/lib/strings/p5-e.ts:5).

  4. Press Mark all as read to clear the unread badge without dismissing any row.

A worked example

Eight kinds of notice exist, and five of them always reach you regardless of any preference — a blocking approval, a run failure, an access change, a routine's health, and the digest. Everything else is a preference you or your bot's own settings decide:

export function shouldNotify(kind: NotificationKind, prefs: NotificationPrefs): boolean {
  switch (kind) {
    case 'approval_needed':
    case 'run_failed':
    case 'access':
    case 'routine_health':
    case 'digest':
      return true;
    case 'run_finished':
    case 'routine_event':
      return prefs.notifyOnFinish;
    case 'update':
      return prefs.notifyOnUpdates;
  }
}

A new bot's notifyOnFinish starts on and its notifyOnUpdates starts off (packages/core/src/notifications.ts:24-27), so a quiet inbox by default still tells you the moment a bot finishes or needs you.

What can go wrong

What you seeWhyWhat to do
Nothing here yet.You have no notices — every one has been cleared, or none has been written yet.Nothing to do; the tray fills in as your bots run.
Could not load notifications. Try again.The tray's fetch failed.Close and reopen the bell.
Could not update that notification. Try again.Marking a row read, dismissing it, or marking all read did not save.Try the action again.

See also

Last verified against build c0f77aa.