🎵 dsh-task-complete-sound — know when your agent finished, even from another tab

[CityNanFlower]

🎵 dsh-task-complete-sound — know when your agent finished, even from another tab

A web GUI plugin that plays synthesized notification cues when a task or agent turn completes — no audio assets, no network requests, everything is generated live with the Web Audio API.

What it does

• 🔔 Four event classes, each with its own tone: turn end, background completion, approval pending, error end (approvals are always audible — even during quiet hours, and exempt from burst merging)
• 🎨 8 synthesized tones (chime / ding / bell / bubble / shimmer / woodblock / storm alarm / silence) with per-event preview
• 💬 Desktop notifications with click-to-jump to the owning session, foreground suppression, and 2-second burst merging (rapid events merge into one "N completions" notice instead of a sound storm)
• 🏷️ Tab-title flashing (✅ / ⚠️ / ⛔) while the page is hidden
• 🌙 Quiet hours (crosses midnight), current-session muting, mute-by-title-keyword (approvals & errors always get through)
• 🧭 Source classification: notifications say whether the completion came from your main session, a subagent, or a scheduled automation task
• ☁️ Config syncs across browsers and the desktop client via the host settings namespace (localStorage fallback)
• 🧪 An event-trace line in the settings card shows where every event went — played / muted / merged / gated — so "test works but real events don't" is always diagnosable

Compatibility: tested on dsh 0.1.7 and 0.2.0-rc.1 (web profile).

Install (Windows PowerShell; respects DSH_HOME, hot-reloads, no dsh restart needed):

git clone https://github.com/CityNanFlower/dsh-task-complete-sound.git
cd dsh-task-complete-sound
.\install-task-complete-sound.bat

Refresh the GUI page and configure under Settings → Web UI plugins → 任务完成提示音. Full docs in the README.

Repo: https://github.com/CityNanFlower/dsh-task-complete-sound

One implementation note that might save other plugin authors some pain: in the cordis client, any service-surface property that is not in your inject list can throw on mere property access — accessing an optional service getter (e.g. remoteFace.schedule from the schedule plugin) without a guard killed the entire apply() and made the plugin silently vanish from the UI. node --check can't catch that; wrap every optional access in try/catch (v0.4.1 lesson, documented in the README changelog).

Feedback welcome — especially from non-Windows users (it should be platform-agnostic since everything is synthesized in the browser, but I've only tested on Windows).