Tauri Notification API: Suppressing Default Sound Unavailable

Question

Silent Notifications in Tauri
The current Tauri notification API (tauri::api::notification) exposes only title, body, icon, and a callback. It does not provide a flag or field to suppress the default notification sound on any platform.
On macOS, silent notifications require a silent key in the userInfo dictionary, but the Tauri API does not expose this key. On Windows, the underlying ToastNotification can be silent by setting the Silent property, yet the Tauri wrapper does not surface this property in its Rust‑side struct or the JavaScript API.
Because the API lacks a silent option, developers cannot request silent alerts through the public interface, and the repository contains an open issue and a pending pull request proposing a silent boolean in the notification payload.
Unresolved Decision
Should a silent flag be added to the notification payload, and if so, how should platform‑specific silent‑notification semantics be handled?
Specific Questions

What is the current status of the open issue and pull request proposing a silent flag in the Tauri notification API?
How would a silent flag be implemented consistently across macOS, Windows, and Linux given their differing notification frameworks?
Are there documented workarounds or plugin extensions that allow silent notifications in the meantime?

Tasadduq Burney · Answer

Direct Answer
The Tauri notification API does not expose a silent flag. Through tauri::api::notification::Notification or the JavaScript equivalent, you can set title, body, icon, and a callback, but there is no supported field to suppress the default notification sound on macOS, Windows, or Linux.
Confirmed Facts and Likely Explanation
Confirmed: the public Rust and JavaScript notification payloads expose title, body, icon, and handler callbacks only. Default sound is controlled by the native backend, not by Tauri's portable options.
Likely explanation: macOS, Windows, and Linux use different notification frameworks. A portable silent flag would need to map to macOS userInfo sound keys, Windows ToastNotification audio suppression, and Linux daemon hints that may not exist. Because those semantics differ, Tauri has not unified them behind a single boolean.
Unverified: any open issue or pull request proposing a silent boolean. Treat its status as unresolved; it may be closed, merged, renamed, or superseded, and it is not guaranteed in any released version.
Steps for This Case

Confirm your target platform and Tauri version. Run tauri --version or inspect Cargo.lock for the tauri version.
Inspect the local notification module for unreleased silent support: grep -rn "notification" src-tauri/src/api/
If you need silent notifications now and upstream lacks the field, use a custom Tauri plugin or native command that calls the platform notification API directly. On macOS, set the sound key to none; on Windows, construct a silent toast. Document that Linux may ignore the request.
As a non-code fallback, use OS-level Do Not Disturb or notification settings. Silent does not mean invisible: banners, badges, and focus behavior may still occur.

Missing Diagnostic Detail
Which operating system and Tauri version are you targeting? That detail changes the recommendation: a custom plugin is only worth building if the target platform supports programmatic sound suppression and your Tauri version does not already expose it.

Tauri Notification API: Suppressing Default Sound Unavailable

Silent Notifications in Tauri

Unresolved Decision

Specific Questions

1 answer

Direct Answer

Confirmed Facts and Likely Explanation

Steps for This Case

Missing Diagnostic Detail

Your perspective belongs here.

0 question comments