You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Voice mute also hides /notify desktop banners, while the doc says it gates TTS only #2784
LIFEOS/DOCUMENTATION/Notifications/NotificationSystem.md (§ Global voice mute) says the mute "gates TTS only — desktop notifications still show, and /notify still returns success while muted."
LIFEOS/PULSE/VoiceServer/voice.ts, in sendNotification, does otherwise:
While the voice is muted, /notify with voice_enabled: false returns {"status":"success","message":"Notification sent"} and shows nothing. Scheduled callers that use the silent banner as their channel (for example CommitmentSweep's overdue / due-today notice) disappear for as long as the mute stays on, and nothing records it.
Repro (Linux, notify-send present)
curl -X POST localhost:31337/voice/mute -d '{"muted":true}'
curl -X POST localhost:31337/notify -H 'content-type: application/json' -d '{"title":"t","message":"m","voice_enabled":false}' → success, no banner.
notify-send t m from the same session → the banner shows.
Question
Which one is intended? If the mute is meant to hide banners too (for example during a recording or a call), the doc line is wrong, and silent-banner callers need another path while muted. If the mute is meant to gate TTS only, the condition should apply only to the voice. A banner on every turn's closer while muted may be why the condition is there.
Locally we left voice.ts as is. Our one scheduled banner calls notify-send directly, so the mute does not hide it.
🤖 Kai (AI assistant) responding on behalf of Daniel Miessler
Thanks @drpaulobernardy, this was a careful report. The mute hiding banners is intentional: we decided on 2026-10-24 that pausing the voice pauses the desktop banner too, since the mute is the kill switch for recordings and calls (LIFEOS/PULSE/VoiceServer/voice.ts, sendNotification). The doc line saying banners still show was out of date and you were right to flag it. We've corrected NotificationSystem.md, and that ships in the next public release after 8.761.0. Your approach of calling notify-send directly for a banner that must survive the mute is a fine one.
Activity
danielmiessler commentedon Nov 12, 2026
Note
🤖 Kai (AI assistant) responding on behalf of Daniel Miessler
Thanks @drpaulobernardy, this was a careful report. The mute hiding banners is intentional: we decided on 2026-10-24 that pausing the voice pauses the desktop banner too, since the mute is the kill switch for recordings and calls (LIFEOS/PULSE/VoiceServer/voice.ts, sendNotification). The doc line saying banners still show was out of date and you were right to flag it. We've corrected NotificationSystem.md, and that ships in the next public release after 8.761.0. Your approach of calling notify-send directly for a banner that must survive the mute is a fine one.