Notifications & Silence (when Omniscio is allowed to interrupt you)
Everything that decides when Omniscio is allowed to pull you back in — OS toasts and their three-way behavior, the chimes each alert type plays, mobile push — and every rule that quiets them again: per-session dedup, a global cap on how often any sound plays, and the moments the app knows you are already looking.
On this page
What it is
What it is — Notifications in Omniscio are the part of the app
Notifications in Omniscio are the part of the app that yanks you back in when an agent needs you. They show up as native OS toasts, optional chimes (each of three alert types has its own sound: needs-you, stalled, error), and — on mobile — browser push. You can mute globally for a fixed duration or indefinitely, mute specific projects, tune when OS toasts appear (always, only when Omniscio is backgrounded, or never), pick built-in or custom .wav/.mp3/.ogg sounds up to 5 MB, and set a separate volume slider for app sounds vs OS-level notification behavior. Once you've sent a reply, post-send navigation decides where you go next. By default it is a priority ladder that moves you to the next session that needs attention in this project, then the next one in the inbox, and only stays on the session you just replied to when there is nowhere else to go. If you would rather deep-focus in one session, set the ladder to just stay.
Where to find it
Settings → Notifications — one pane holds the whole picture, including the Recent chimes log of what played and what was silenced.
How it behaves
How to use it
- Find the settings. Open Settings → Notifications. Everything lives in one pane.
- Control when OS toasts appear. The Notification behavior radio set is three-way: Always (even when Omniscio is focused), Only when backgrounded (the common sweet spot), or Never (rely on sounds + in-app toasts only).
- Mute temporarily. Use the Silence until picker — choose a preset like "1 hour" / "tomorrow 9 am" / "indefinite", or pick a custom timestamp. You'll stop getting toasts and sounds until that time. Clear it to resume. You can also mute specific projects in the Per-project mutes list.
- One-click toggle from the header. The bell icon in the header toolbar flips indefinite silence on/off in a single click (a struck-through bell means muted). If you've unpinned the bell so it lives in the header's "…" overflow menu, clicking the Notifications row there does the same thing — you'll get a brief "Notifications muted" / "Notifications unmuted" toast since the menu can't show the bell's icon state.
- Customize sounds. Flip Notification sounds enabled on to get chimes (plays regardless of OS toast behavior — so "Never" + sounds on still audibly alerts you). Each of the three alert categories has its own picker: built-in (alert-ping, attention, bright-ascent, classic-ding, digital-tone, gentle-chime, mission-alert, rising-chime, soft-bell, soft-marimba-link-ready, soft-marimba-upload-done, subtle-pop), your OS system sounds, or a custom file you upload. Slider sets volume 0–100%. The screen recorder's two completion cues (link ready, upload done) default to the soft marimba pair and are set from the same pickers; a recording plays at most one of its link-ready cue and its saved chime.
- Tune post-send navigation. Two settings (Settings → Workflow) control where you land after sending a reply. After sending a message is a priority ladder that defaults to next attention session in this project → next in inbox → stay. After sending while in inbox (labelled "Auto-advance in inbox", default on) moves you to the next inbox item that needs you, or clears the panel if none remain. Choosing "Stay on session" there always stays on the session you answered, whatever the "After sending a message" ladder says (2026-11-04; before that it handed the reply to the ladder, which by default still advanced in the inbox). The session you just answered stays open on screen even though it has left Needs You, until you move to something else yourself — nothing else in the inbox is opened for you. Match these to how you triage: the defaults suit working a queue front-to-back; if you deep-focus in one session, set the ladder to just stay. The ladder applies in a normal project and the inbox; inside a hub screen (Mission Control, Tasks, Overseers and the other built-in hubs) a reply always stays on the session you answered, because those screens host their own conversation. The first message in a session you just started is the one exception to that ladder: sending it puts you back where you were before you clicked New, so a brand-new conversation never strands you on itself. If the place you came from was an empty, unused chat (nothing sent, nothing typed), that chat is skipped one level and you land on the chat you were in before it — and when there is nothing there to go back to, you simply stay on your new session.
- Mobile push is separate. Mobile sound enabled and Web push enabled control the phone experience independently — handy if you want quiet on the desktop but a chime on the phone when you step away.
- Hide content in mobile notifications (privacy). Hide content in mobile notifications is ON by default — the privacy-safe posture, so your phone's lock screen and the push provider that delivers the notification never see the actual message. With it on, an incoming text / email / session alert arrives as a generic "New message" / "New email" / "Session needs you" instead of the sender, subject, body, or session name; tapping it still opens the right conversation on the phone. Turn it off if you'd rather keep the at-a-glance preview (sender, subject, body) on your phone.
- Turn the app-icon badge on or off. Your app icon (Windows taskbar / macOS dock) shows a small count that mirrors your Inbox — the same number shown on the in-app Inbox (every inbox item, not just sessions that need you). App icon attention count (default on) controls it: turn it off for a plain icon with no badge, and the badge updates immediately (no restart). Focus Mode and Presentation Mode already clamp the badge to 0 while they're on. There's also a one-tap Feature Discovery Nudge that offers to flip this right from your inbox — a live on/off switch in the card.
When desktop pop-ups stop arriving
If a desktop pop-up that should have appeared does not, Omniscio raises one inbox card — "Desktop alerts aren't reaching you" — instead of failing silently, because a dead pop-up channel is invisible otherwise: the app looks healthy while every "needs you" notice slips past you. The card is raised once per outage, never once per missed pop-up, and it says the part that matters: the inbox still receives everything, so nothing is waiting unseen.
Archiving it sticks. Once you put the card away, it stays away — a pop-up the computer then refuses counts as one that never arrived, so it does not bring the card back. That is what used to happen on Windows when the app's own notification switch was off. Only a pop-up that really makes it onto your screen makes the card raisable again, so archiving it is a real answer rather than a button you have to press twice.
On Windows it can now name the actual cause. Windows keeps a per-app notification switch at
HKCU\Software\Microsoft\Windows\CurrentVersion\Notifications\Settings\<app id> (value Enabled),
and turning an app off there is a common reason for pop-ups to vanish while the app itself looks
fine. When Omniscio finds that switch off for its own app id, the card says so and gives both fixes
in plain words: turn it back on under Windows Settings → System → Notifications → <the app>
(older versions of the app are listed there under an earlier product name), or use the card's
Turn off desktop notifications button if you would rather not have pop-ups at all. The button
turns every OS toast off and leaves the inbox untouched, so you keep the alerts and lose the
interruptions. When the app cannot read that switch — a different platform, a key that does not
exist yet, a registry I/O failure — the card keeps its general copy about a declined permission or
Do Not Disturb rather than guessing.
Dismissing the card sticks. Archiving it (or turning pop-ups off from it) is remembered across restarts, so it does not come back on the next failed pop-up. It is re-armed by a pop-up that actually appears: the first successful toast clears the memory, which is what makes a genuinely new outage raise exactly one fresh card.
The first pop-up of a launch no longer costs you a freeze. On Windows, the very first desktop notification an app shows is also the moment Windows starts its notification engine for that app — work measured in seconds on a busy computer. Omniscio used to pay that cost on the first alert of a run, which meant the window could stop responding for a few seconds while you were in the middle of something. It now asks Windows for toast support once, while the app is still starting up and the window is not open yet, so a later alert is delivered without that pause.
In-app toast preferences (the unified toast system)
Separate from the OS-toast controls above, the In-app notifications card in Settings → Notifications controls the small pop-ups Omniscio shows inside the app. They are grouped so you tune them by kind, not one at a time:
- Always on (Errors, Warnings) — shown a small "Always on" label, no switch. The toast system's severity gate renders every error/warning regardless of any preference, so "turn off notifications" can never silence "Your message failed to send."
- Confirmations (settings saved, project/session/recipe/deploy actions, screenshot captured) — receipts for actions whose result you can already see. The "Show confirmation toasts" master switch at the top flips this whole group on/off in one click, or toggle just one — e.g. Screenshot captured silences the "Screenshot saved and copied to clipboard" pop-up while capture failures still show. To keep first-run quiet, the lowest-value receipts — Settings confirmations and Project changes — default off (the change is already visible in the panel / sidebar); flip them on if you want the confirmation.
- Deletions and Notices (copies, account activity, budget/usage, status, voice, and other one-off results) — per-category toggles. Two deliberate default choices here: the highest-frequency, lowest-value receipt — Clipboard copies — defaults off to cut out-of-box noise, and both session alerts — Status alerts (a session errored / stalled) and Attention alerts (a session needs your input) — default off, because the inbox already carries every session event. Their off switch is absolute: even though these toasts are coloured as warnings/errors, switching them off silences them completely (other error and warning toasts still always show).
- Tasks: three switches for everything the Tasks feature tells you, all on by default. Finished tasks covers "Task complete", a repeating task's next date and finishing several at once; Task changes covers moves, reschedules, deletes and dismissed suggestions; Tasks tips & hints covers guidance such as "switch to manual sort", the keyboard tour offer and Tasks AI status. The gear on any Tasks toast opens its own switch here. Turning Finished tasks off silences the pop-up only; Undo (Ctrl+Z) still works. Tasks error and warning toasts follow the Always-on rule.
- Team Chat: three switches for everything Team Chat tells you, all on by default. Messages covers sent, edited, copied, scheduled and pinned messages, unread-copy and offline saves, the attachment warning when you start a session from a message, and a call ending; Channels & workspaces covers channel, topic, custom-emoji and workspace changes, webhooks, forum feeds and imports; People & roles covers members added or removed, role changes, email invitations and guests. Creating a task or a PM item from a message files under Task changes instead, because the task is what changed. Turning a switch off silences its pop-ups only — nothing in Team Chat stops working.
- Marketplace & plugins: two switches, all on by default. Automations covers installing, importing, publishing and reviewing a shared automation; Plugins & access covers plugin installs and updates, plus the approvals for the data a plugin can reach.
- Alerts & inbox: two switches, all on by default. Alert actions covers dismissing, assigning or acting on an alert and replying from one; Inbox actions covers archiving, replying, reassigning and other changes made from the inbox. Adding an inbox item to your tasks files under Task changes instead, because the task is what changed. A reminder that fires on its own is an alert, not an action — those keep their own switches above.
- Sessions: three switches, all on by default. Agent Access covers what the agent may do without asking and changes to that; Session tools covers switching the harness, the composer, recipes and gates from the session toolbar; Session exports covers exporting a session or a file and converting an attachment to Markdown.
- Writer: two switches, all on by default. Documents covers saving, publishing and changes made to a document in another window; Send to Tasks & Team Chat covers sending a document to your tasks or to Team Chat.
- Browser: two switches, all on by default. Browser actions covers inline edits, design mode, skills and workflow recording in a tab; Logins & autofill covers a saved login or a login form spotted on the page.
- AI Coaching: two switches, all on by default. Records & imports covers imports, restores, labels and life-inventory results; Profile & goals covers saving or regenerating your profile and goals moving between filters.
- Notes & knowledge: one switch, on by default, covering what you do in KMS notes, the journal, mind maps and bookmarks — saving, moving, restoring and deleting.
- Settings & setup: two switches, all on by default. Settings changes covers what you save, export, reset or connect from inside Settings; Setup & onboarding covers the steps and tips while you finish setting up.
- Media: two switches, all on by default. Images & decks covers saving markup, upscaling, and exporting images, storyboards and decks; Recordings & voice covers screen recordings, clips, permission prompts and saved voiceprints.
- Mail & messaging: four switches, all on by default. Email covers starring and marking read; Messages, meetings & replies covers texts, Teams, meetings, shared items and quick replies; Boards covers links and invites on Linear, Notion and Monday; Scheduled work covers starting, finishing or aborting a scheduled run.
- Calendar: one switch, on by default, covering adding and removing events in your Google Calendar.
- Workspace: two switches, all on by default. Layouts & shortcuts covers switching and resetting layouts and keyboard-shortcut hints; Scripts & tools covers launching a script, opening the demo window and repairing missing icons.
Below the toggles, the Error/warning display time dropdown controls how long error and warning toasts stay on screen before auto-dismissing. Preset options are 5, 8, 10, 15, and 30 seconds; the default is 8 seconds (matching the previous hard-coded duration). Success and info toasts are unaffected — they use the fixed receipt duration (3 seconds on desktop, 1.5 seconds on a phone). A toast that carries an action, such as Undo, keeps its button reachable for 5 seconds on any device, phone included. If a caller passes an explicit duration when creating a toast, it overrides this setting.
Below that, the Recent notifications inspector is a live, newest-first log of what just popped up (in-memory, resets on restart). Each row shows the category, how long ago it fired, and the message, with a one-click mute that turns that category off on the spot — always-on rows show "Always on" instead. It is read-only; it never fires a toast itself.
Under the hood every in-app toast flows through one gated entry point, notify(), so the
severity gate and per-category preferences can't be bypassed. Full invariants:
unified-toast-system-contract.md.
Desktop pop-ups have one funnel too. Every OS notification goes through the notification service, so Silence all, "Never" and Focus Mode apply to all of them — including an automation's own Notify me action and its Summarize → notification destination, which until 2026-09-28 popped up even while everything was silenced (the run log now says when your quiet settings held one back). Because nothing else in the app shows that notice, when only the desktop pop-up is off — "Never", or Omniscio is in front under "Only when backgrounded" — it appears as a message inside the app instead, and it plays the app's notification sound under your sound settings. The only pop-ups outside the funnel are three receipts for something you just did yourself: opening the app a second time, a Quick Launch that failed to start, and a screenshot you just took. A build check fails if any other code builds a raw pop-up.
On mobile, in-app toasts never cover the chat box. The moment you focus a text box and the on-screen keyboard comes up, the toast stack moves to the top of the screen — so a notification never covers what you're typing into or hides behind the keyboard. And whenever the chat box is on screen with the keyboard down, notifications float just above it instead of landing on top of it — dropping to the usual bottom spot only when there's no chat box in view. Desktop is unaffected. Behind the scenes: keyboard-viewport-contract.md.
Pipeline lane silence
Sessions spawned by a recipe's pipeline-expansion step (one per lane × per pipeline stage) are flagged is_pipeline_lane=true and never fire a notification — chime, OS toast, or mobile push. This is unconditional: it ignores Silence until, ignores per-project mutes, ignores the showRecipeLaneSessions visibility toggle (which controls whether the lanes appear in the sidebar at all), and is independent of the alert_armed per-session dedup. The orchestrator session itself and any mainline steps you authored (consolidate, approve, repair) still notify normally — you hear the run finish or an approval ask, you just don't hear each of the 132 audit lanes ping individually.
Per-session alert dedup
Errored / stalled sessions no longer chime (updated 2026-08-11). Error and Stalled were reclassified as non-attention, so they now raise no chime, no OS notification, and no inbox row — they go quiet in the sidebar's Interrupted group. Only Needs You chimes now (a genuine "Recovery failed" give-up stays quiet too: it waits in the Interrupted section with no chime and no inbox row). The dedup rules below still apply to the Needs You chime; the mentions of Stalled / Error describe the pre-2026-08-11 behavior.
When a session fires a Needs You / Stalled / Error alert, it immediately disarms itself — that same session won't fire another alert (chime or OS toast) until it is re-armed. Other sessions are unaffected: if Session A is disarmed and Session B hits Needs You, B fires normally.
The goal is one chime per arrival into an attention state — you hear it each time a session genuinely becomes Needs You / Stalled / Error, but a session already sitting in your inbox doesn't keep pinging.
What re-arms a session — two triggers, either one is enough:
- A genuine transition back into an attention state. When a session leaves attention (e.g. you reply and it returns to running, or auto-continue picks it up) and later transitions into Needs You / Stalled / Error again, that re-entry re-arms it — so the next arrival chimes. This is what makes the chime fire "every time something finishes," not just the first time after a reply.
- A human-authored reply via
IPC.SESSION_SEND_RESPONSE— the composer, question-widget answers, plan approvals, snippet sends, and mobile WebSocket sends.
What does NOT re-arm: churn within attention (e.g. Needs You → Error on the same session, or a repeated Needs You with no intervening non-attention status) — the session was already alerted, so mid-stream status changes don't re-chime. Passive actions don't re-arm either: opening / viewing the session, clicking the OS toast, or a Send Later delivery. (Clicking Continue or auto-continue doesn't re-arm by itself, but the session's later transition back into attention will.)
What is NOT gated: mobile push (the phone alerts always come through, intentional design), the visible amber sidebar dot (the session still shows in attention lists), and badge counts.
Transient process blips stay quiet: if a session briefly loses its underlying process and Omniscio automatically restarts it (common under heavy load), it flips red for a moment but does not chime — the error sound is saved for a failure that actually sticks. The same holds when a session is rehydrating after Omniscio itself restarts (an app crash + auto-restart): while it's being brought back it can flicker into an error state, but that self-healing blip is silenced too, so you never hear a chime you can't find in your inbox. You still see it in the sidebar; you just won't get a false alarm for something that fixes itself on its own.
A scheduled (cron) job that hits a usage limit stays quiet too: when a cron job fails specifically because it ran into a Claude usage or weekly-rate limit — a benign capacity condition that clears on its own once limits reset — Omniscio treats it as a capacity park, not an alarm. It plays no error chime (and Omniscio won't auto-spawn a fix-it session that would just hit the same limit), but the failure still shows its card in your inbox with the real reason, so you can see it without being jolted by a sound for something you can't act on. An ordinary cron failure (a real bug) still chimes as before.
Persistence: the armed/disarmed state is stored on the session row (alert_armed column, schema v96) so it survives app restart.
Full contract: the arm/disarm writers, the seven-gate fire cascade (pipeline-lane → snooze → recovery-in-flight → arm → overlay → Focus Mode → fire), and the test-locked invariants live in notification-chime-contract.md — read it before changing any chime behavior. The recovery-in-flight gate is what silences the transient blips above: a session being auto-recovered (an app-restart resume episode, a rate-limit auto-switch, an auto-resumed suspend, or a lost-contact revive) yields the chime while it self-heals, mirroring the fact that the inbox already hides it (invariant I10).
Global per-minute sound cap
Separate from the per-session dedup above, a global hard cap limits how many notification sounds of any variety play per rolling 60 seconds — across all sessions and all three alert types combined (currently 1 per minute). Where the per-session dedup stops one session from re-pinging, this stops a storm of many sessions from becoming a barrage: if 30 sessions hit Needs You at once, you hear at most one chime that minute, not thirty.
It's enforced in the background process — the single function every notification sound flows through — so it survives a window reload (the on-screen cooldown doesn't), and it caps audio only: every session still turns its sidebar dot amber/red and still appears in your attention lists, only the sound is throttled. Scheduled alarms, read-aloud (TTS), dictation beeps, and the sound-preview buttons in Settings use separate audio paths and are never capped.
Locked as invariant I9 in notification-chime-contract.md.
On-screen quiet (when you're already looking)
Two smaller, on-screen rules sit in front of the actual sound — separate from the per-minute cap, and they only affect the desktop chime:
- You're actively working the Inbox (15 seconds). If you've just clicked, typed, scrolled, or tapped in the Inbox, a new chime stays quiet for 15 seconds — you're already looking, so the ping would be redundant. This counts only real interactions: moving the mouse or bringing the window to the front does not count. (A fix in Aug 2026 — before it, a cursor drifting over the Inbox could swallow every needs-you chime while the history still claimed "Played.")
- Back-to-back cooldown (10 seconds). Two chimes within 10 seconds collapse to one. Under the 1-per-minute cap this rarely comes up; it's a last-resort debounce that lives in the window (so it resets if you reload).
Both now tell the truth in Recent chimes below: when the desktop drops a chime for either reason, the window reports back what it actually did, so the log records it as Silenced (with the reason) instead of a false "Played."
Recent chimes (chime history)
Heard a chime but not sure what it was? Settings → Notifications → Recent chimes is a persistent log of the last chime decisions — every sound that played, plus every one that was silenced and why (a self-healing restart blip, a snoozed session, the per-minute cap, or because you were already active in the Inbox). Each row shows the session, the kind (Needs You / Stalled / Error), whether the sound actually played, and how long ago. Unlike the in-app Recent notifications toast inspector higher up the pane (in-memory, resets on restart), this survives restarts — so a chime you heard minutes ago is always accountable. Turn it off with Save notification chime history (on by default); when off it records nothing and never touches the sounds themselves. It is bounded (newest entries kept, older ones pruned) and read-only. Locked as invariant I11 in notification-chime-contract.md.
Alerts from plugins
A plugin that has the notifications permission can raise a desktop notification with
toast.notify (or notifications.fire). Both reach the same place and obey the same rules as
every other desktop pop-up here: Silence all, the when to notify behavior, Focus Mode and
project mute. Two alerts with the same title and body replace each other instead of stacking.
The plugin-facing description is plugin-bridge-capabilities.md.
Related
Related — snooze-a-session.md
- snooze-a-session.md — snooze silences a single session rather than the whole app
- session-stuck-in-needs-you.md — why you got an alert
- account-pool.md — the exhausted-accounts OS notification respects these global controls; the in-app banner does not
- The dedup also gates Stalled and Error alerts — see
notifyNeedsYou/notifyStalled/notifyErrorin notification-service.ts for the gate
Last verified 2026-11-11