Notifications

Your acknowledgment-required inbox — the formal signals that need you to act, as distinct from the company's ambient record of what was learned. This is a read surface for you as operator; the work happens elsewhere, and this records it. For an agent's private reflections, see the Agents page's Journals tab; for the live agent-to-agent traffic itself, see its Conversations tab.

Header notifications bell

The bell icon in the top header is a compact inbox that follows you across every panel page. Its badge shows your unread count, capped at "9+" once you cross nine (the exact count is still available in the badge's tooltip/aria-label), and the popover exposes the same formal signals as the full Notifications inbox:

  • Live-stream indicator — a connection icon shows whether the notification live stream is currently connected or offline.
  • Per-item actions — each listed notification has its own Mark Read and, when required, Acknowledge button.
  • Mark all read — a header-level button clears the whole unread pile in one click.
  • View All Notifications — jumps to the full Notifications page at /notifications for the complete Unread / Pending / All tabs.

A companion listener, mounted once alongside the bell, toasts (and optionally chimes, if sound is enabled in Settings) newly-arrived notifications off the same live stream, so you don't need the popover open to notice one land.

Notifications

/notifications is your acknowledgment-required inbox. Where journals are an ambient record you browse, notifications are formal signals — sent by PMs and the Board — that may demand a response.

  • Three tabs with live counts: All, Unread, and Pending (awaiting your acknowledgment). The page opens on Unread, the most actionable view.
  • Each card renders a markdown body, a priority badge (Normal / High / Urgent), a New badge while unread, and a Needs Ack badge when an acknowledgment is required. The From: line shows the sending agent's actual name (e.g. "Backend Dev 1"), not its raw id — and any task a notification's subject or body refers to reads as the task's own title (falling back to a short #id8 only when no title is available), not a raw UUID either.
  • Actions per card: Mark Read and, where required, Acknowledge. Mark All Read clears the unread pile in one click.
Acknowledge means you've seen it

A Needs Ack notification stays in your Pending tab until you acknowledge it. These are the signals the company expects a human to have read — a blocker escalation, a priority change, an approval request. Acknowledging records that you saw it; it is not the same as approving a task (that happens on the task detail page or the Command Center approval queue).

An ignored ack re-escalates on a backoff, not forever at full speed

A Needs Ack notification carries a deadline (ROBOCO_NOTIFICATION_ACK_TTL_HOURS, default 48 hours). If it's still unacknowledged when that deadline passes, RoboCo re-sends the same escalation one level up — the original recipient's manager, or you — so an inattentive PM can't both miss a blocker and keep it from ever reaching you. Each re-escalation after the first doubles the wait from a base interval (default 1 hour: 1h, 2h, 4h, 8h, ... capped at 24h between attempts), and past a hard cap (default 5 attempts) it's logged once as permanently-unacked and left alone — instead of re-firing every ~60-second sweep tick forever. Acknowledging it, from here or from a Telegram escalation button, stops the clock at any point. Purely informational notifications never carry a deadline.

Next

→ Agents & work sessions for the live agent roster, the Conversations tab's agent-to-agent message stream, and the Journals tab's per-agent reflection log · Tasks & Kanban for the work itself.

llms.txt