Skip to content

Notification center ​

The notification center keeps the alerts Clusto raised, so you can see what happened while you were away. It is the Attention view, which shows only this history (see Attention list).

Open it with Mod+I (outside text fields and terminals), Mod+Shift+A, the bell in the sidebar header, or Open notification history in the F1 palette. It is free on every plan.

What it lists ​

Each entry is an alert such as an agent waiting for an answer, a finished agent turn, a task result or a new report. Entries are grouped, and you can switch the grouping between:

  • Session and Chat - alerts from one terminal or chat together. If the session has ended or the chat was deleted, the entry says so ("This session has ended", "This chat no longer exists").
  • Project - alerts from the sessions and chats of one project.
  • Category - alerts that do not belong to a conversation: Tasks, Factory, Reports, GitHub, Azure DevOps and Other.

Selecting an entry opens what it is about. Show more loads older entries.

Choose what to show and count ​

The Filter button in the Attention header opens a Show and count popover with one row per kind of alert: Waiting for your answer, Terminal agents, Chat replies, Tasks, Factory, Reports, GitHub, Azure DevOps and Other. Each row has two checkboxes:

  • Show lists that kind in Attention.
  • Count adds it to the bell badge and the Attention navigation badge.

A kind you hide never counts, whatever its Count box says. Reset to all restores the default, everything shown and counted. A dot on the Filter button marks a filter that differs from the default. The same popover opens from Attention: choose what to show and count in the F1 palette while you are on Attention.

The choice is a synced preference (clusto-attention-filter), so it follows you through account cloud sync and cluster preferences to every device. It is free on every plan.

Read state ​

An entry is Unread until you open it, mark it read or choose Mark all read. Read state is shared across the cluster: reading an alert on your phone marks it read on your desktop. The first time a node has a history after an upgrade, the older alerts are marked read, so you do not start with a wall of unread items.

Some alerts also read by themselves when what they point at is read:

  • A chat alert (Reply is ready) reads once that chat is read. Opening or interacting with the chat, on any device, clears the unread dot and the bell count. A later answer in the same chat raises a new unread alert.
  • A report alert reads once the report is read or archived in Reports.
  • Reading an Azure DevOps pull request or work item in the Azure DevOps view (opening it, or that view's Mark all read) reads its alerts.

What is on screen reads its alerts too, including alerts that arrive while it stays open. Alerts that arrived while the window was in the background are read when you return to the window. A focused terminal reads its terminal session alerts (the same rule as its bell), an open GitHub pull request or issue reads its GitHub alerts, and an open Azure DevOps pull request or work item reads its alerts.

To clear alerts without opening them, use the check buttons. Every unread row has its own check button that marks just that alert read. While a group card (a session, chat, project or kind of alert) has unread alerts, its header shows a Mark all in ... read button that names the group, which marks every alert in that group read. Both lower the unread count and sync across your devices like any other read mark.

Mark all read clears everything, not only the alerts: every alert, every unread chat, every unread Azure DevOps pull request and work item across all accounts (the Azure DevOps nav badge clears), every report in the feed (marked on the server, loaded or not), and the terminal bell markers in the sidebar. The button and the F1 palette command Mark all notifications read show whenever any of those has something unread, even when the list itself has nothing unread. If reports cannot be marked, a toast says so.

The GitHub nav badge counts reviews waiting on you. It is not read state, so Mark all read does not clear it.

Answered prompts ​

When an agent waited for an answer and then continued, its alert is marked Answered instead of staying pending. An answered prompt no longer counts on the bell and is not raised again by the Android background check.

Retention ​

Each node keeps its last 7 days of alerts, up to 500. Older ones are dropped. The list shows alerts from every node you can reach, so the oldest entries from an offline node appear when it returns.

Clusto - remote AI coding agents over WebSocket.