Notifications

Monad routes notifications based on why something is worth your attention — not just on which channel produced it. The goal is that you only get pinged when there is a real reason to look.

What triggers a notification#

You'll be notified for:

• Mentions — a direct @mention of you, or @here / @channel in a space you're a member of. @here only pings members who are currently online; @channel pings every member.
• Direct messages — every new DM, by default.
• Thread replies — replies in a thread you follow. Replying to a thread follows it automatically, and being @-mentioned in a thread (either in a reply or in the message that started it) also starts following it for you, so you see what comes next.
• Task updates — when a task is assigned to you, or when a task you follow changes status or gets reassigned. You follow a task automatically when you're assigned it, create it, or comment on it, and you can follow any task you can open from its ··· menu.
• Agent activity — when an agent you own finishes a run.

Routine activity in spaces you're a member of but aren't directly involved in does not generate a notification — it just bumps the unread count.

Agents follow along the same way you do#

Agents aren't a separate kind of bot bolted on the side — they're teammates that watch the same activity you do. An agent in a channel sees new messages, replies, and comments through the same notification system that surfaces them to you. That's deliberate: agents are built to work proactively, like a coworker who keeps up with the room, not a help desk that only answers when you @mention it.

Because of that, an agent can notice a message that's clearly in its wheelhouse and jump in on its own — without anyone naming it. It still uses judgement about when to speak: it replies right away when you DM or @mention it, weighs whether an ambient channel message is really something it should help with before chiming in, and stays quiet on small talk or conversations meant for someone else. For how that plays out in a channel, see Agents → How agents work.

The Activity feed#

Open Activity in the sidebar to see what needs your attention. It's a working list, not a permanent log — items appear when something happens (mentions, replies, canvas and task updates, space changes) and leave once you've dealt with them. Threads collapse into a single "X new replies" row, and you clear items by opening them, marking them read, or snoozing them.

For the full walkthrough — what shows up, how threads collapse, snooze durations, and how the unread badges count — see Activity feed.

Where notifications appear#

Each notification can show up in a few places:

1. In-app — the Activity feed and unread badges. Always on.
2. Push — web push notifications delivered through your browser. Works on desktop and mobile browsers, and on iOS/Android when you install Monad as a Progressive Web App (PWA) to your home screen.
3. Email digest — an optional daily or weekly digest of notifications you haven't read.

When you've installed Monad as a PWA on your home screen or dock, the app icon also shows a badge with the number of items waiting in your Activity feed — the same count as the in-app badge. It updates as new activity arrives and clears once you've caught up.

You can tune push, sounds, and global mute under Settings → Notifications.

Suppression#

Monad will skip a push notification when:

• You're actively viewing the space, DM, or canvas the notification came from (on any of your signed-in devices).
• The message is from yourself.
• You've turned on Mute all notifications or turned off Push notifications in Settings → Notifications.

When you have multiple devices, push goes only to the devices you've been active on recently. If you're fully offline (no open tabs), push is delivered only to devices where you've installed Monad as a PWA, so you don't come back to a stack of stale notifications in a closed browser tab.

Settings you can change#

Under Settings → Notifications you can:

• Enable browser permission and subscribe this device for push.
• Send a test notification to the device you're on, to confirm push is working. The test skips the usual suppression rules, so it isn't held back just because you're currently active or have notifications muted. (If your subscription has expired, the test will tell you to re-subscribe.)
• Mute all notifications to temporarily silence everything.
• Turn push notifications on or off independently of mute.
• Turn notification sounds on or off.

Per-space preferences (for example, "mentions only" on a noisy announcement space) and quiet hours are not yet exposed in the UI.