dsh-notify

In real-world use, a dsh agent stops to wait for you constantly: a sandbox-escalation permission needs your confirmation, an ask_user_question prompt is waiting for an answer, a plan review sits in limbo, a turn finishes and the agent idles for your next input, a goal completes or gets blocked, a session errors out, or a tool-workflow run ends. None of these are emergencies, but if your cursor is in another window or tab, they quietly slip past, and by the time you look back the agent has been sitting still for minutes.

dsh-notify takes a deliberately small role. It attaches to the dsh host event bus as a pure observer of those six key moments and fires a native desktop notification at the right instant: osascript system notification on macOS, a PowerShell popup on Windows, notify-send on Linux, a terminal bell, or a fully custom command. The approval and question listeners are strictly passive — they always forward the request onward and never participate in the decision. Notifications are dispatched via detached child processes, so they can never block the agent loop; a failure is merely logged.

Sensible built-in defaults mean all six triggers are on and the channel auto-selects for your platform out of the box. Under the Web profile, a dedicated Notifications tab appears in Settings where you can flip the master switch, pick a channel, tune the minimum interval, enable root-sessions-only filtering, toggle verbose logging, set a custom command, and switch individual triggers on or off. Changes are hot-applied the moment you hit Save — no restart needed.

If you like to keep a dsh agent running in the background while you work on other things, this plugin pulls you back with a single desktop toast at every critical juncture. It does not inject itself into the approval chain, adds no runtime dependencies, and works in any dsh profile once installed.