Choose how the board notifies you

Set up notifications so that what needs you (a plan, a question, a tool request) reaches you wherever you are, and the rest waits quietly. You end with the bell sorted, OS notifications on for the devices you use, and the noise muted.

Before you begin

Nothing to install. OS notifications on a phone need the board installed as an app on an https address; see Reach the board from your phone.

Read the bell

1. In the header, click the bell. A red number counts what needs you; a dot with no number means only updates are unread.

2. Pick a tab:

   Tab	What it holds
   Needs you	A question or a tool request (Needs input), a plan to review (Plan ready), a Loop result that is due (Due now), and a background task that finished while its ticket was parked (Task finished).
   Updates	Everything else: an agent claimed a ticket (Progress), a column move or a merge (Status), a side question answered (Aside answered), a new model, an agent CLI updated.
   Loop	Anything from a Loop or one of its runs.
   All	Everything.

3. Click a notification to open its ticket; that also marks it read.

Notifications are grouped per ticket. On a group, the icons open the ticket, mute it, or mark the group read. At the top, Mark all read clears the lot and Show read brings back what you already read.

Result: you see what waits on you first, and each entry takes you to its ticket.

On a narrow phone screen the bell folds into More actions as Notifications.

Get notifications outside the board

1. Open Settings > Workspace > Browser notifications.
2. Tick Enable notifications on this device.
3. Allow notifications when the browser asks.

Result: this device shows an OS notification when a plan is ready, a question or a tool request is waiting, a Loop result is due, or a ticket reaches In Review, even with the board closed. Clicking one opens the ticket.

The setting is per device: turn it on again on each browser and phone you use. The first time you open the bell, the board also asks for permission and turns this on if you allow it. On iPhone it only works in the board installed as an app (Share > Add to Home Screen), and on any phone only over https.

Mute a kind of notification

1. Open Settings > Workspace > Mute notification kinds.
2. Tick each kind you do not want, for example Mute Status changes (column moves, merge/revert).
3. Click Save changes.

Result: a muted kind creates no notification at all: no bell entry, no OS notification, no Slack post. Progress is muted on a new board, since the card already moves.

Mute one ticket

1. In the bell, find the ticket’s group.
2. Click its mute icon (Mute this ticket’s notifications).

Result: that ticket stops notifying you, whatever the kind. The same icon unmutes it. In Catch up, the mute icon on a card (or M) does the same.

Catch up after time away

1. In the header, click Catch up (the stacked cards icon next to the bell; in More actions on a phone), or press G.

2. Read the card: what happened on that ticket while you were away. A plan or a tool request can be answered right on the card (Accept plan, Reject with feedback, Allow once, Deny).

3. Move on:

   To	Click	Key	Swipe
   Mark it seen	Seen	Right	right
   Leave it for later	Skip	Left	left
   Open the ticket	Open	Up, Enter or O	tap
   Undo the last one	Undo	Down
   Mute the ticket	the mute icon	M

Result: when the last card is done, You’re all caught up. Closing Catch up halfway pauses it, and it picks up where you left off.

Catch up holds one card per ticket with unread news on the current board, questions and plans first, then newest first. Column moves and Progress are left out. Notices that belong to no ticket (a new model, an updated CLI) come last, on one System notifications card.

Act on a new model or an updated CLI

The board tells you, in Updates, about two things that belong to no ticket:

• New model: a new Claude or Codex model is available. Click Make default to make it the Default model, or Not now.
• CLI updated: Claude Code, Codex or Cursor moved to a new version. The board checks at startup and every 6 hours, and updates them itself while Auto-update the agent CLIs is on (Settings > Agents > Model & thinking). Click View changelog to see what changed, or Dismiss.

Neither is sent as an OS notification or to Slack. Mute them like any other kind.

Post notifications to Slack

Slack has no control in Settings: the board posts there when REV0_SLACK_WEBHOOK is set to a Slack incoming webhook. Each new notification posts once as [#<id> <title>] <message>; repeats, muted kinds and muted tickets never post. REV0_SLACK_DUE_WEBHOOK sends only Loop results that are due, to a separate (usually private) channel. See Configuration.

If something goes wrong

Notifications blocked

The browser has notifications turned off for the board’s site. Allow them in the browser’s site settings, then tick Enable notifications on this device again.

Couldn’t enable push on this device

On iPhone, install the board first (Share > Add to Home Screen) and turn it on from the installed app. On any device, the board must be on an https address.

This browser doesn’t support Web Push

The browser cannot receive notifications with the board closed. Use another browser, or keep the board open.

Related

• Reach the board from your phone, to install the board as an app.
• Answer what the board asks you, for what to do with a notification once it arrives.
• Keyboard shortcuts, for every Catch up key.