agentnotifylisted

# AgentNotify Use the installed `agentnotify` CLI to alert the user at meaningful attention boundaries. AgentNotify runs locally, reads its own per-user credentials, and raises a desktop notification without stealing focus. Notifying is the standing default, not something to ask permission for. The user is not watching the terminal; a finished task or a blocking question that is never announced is a task the user learns about late. ## Command name - Windows, and **WSL calling the Windows broker**: `agentnotify.exe` - macOS, Linux, and a Linux-native broker: `agentnotify` Every example below uses `agentnotify.exe`; drop the extension on macOS and Linux. ## Check availability Run once per session, before the first send: ```bash agentnotify.exe health ``` If the command is unavailable or the broker is not running, continue the user's task and report the notification failure only when it is relevant. Do not retry in a loop. ## When to send Send one **without being asked** whenever: - human input is needed — a decision, a permission, an answer that blocks progress — and send it *before* starting to wait, not after; - a task is finished, whatever its size; - work is stopped by a terminal error or an external blocker. Any request to be told when something happens — "ping me when it's done", "let me know if you get stuck", "notify me" — is a request for an `agentnotify send`, for the rest of that session. Do not ask the user which notification mechanism to use. When y