mulmoterminal-notify

Which moments notify you, and how

Running several agents at once is what turns notifications into noise, so the defaults are deliberately narrow: only finished and waiting beep, and the other four are opt-in.

Ask what they actually want to be interrupted for before changing anything. "Turn on all six" is almost never the right answer.

The six moments

Kind	Fires when	Beeps by default
finished	The turn ended; output is waiting to be reviewed	yes
waiting	The agent is blocked on input — a permission prompt or a question	yes
command-done	A Run cell's command exited 0	no
command-failed	A Run cell's command exited non-zero	no
session-exited	A session's PTY ended	no
pr-ci-failed	A directory's PR phase became CI-failing	no

Two of these have caveats worth saying out loud:

• session-exited fires when you close a cell yourself. Closing goes through the same path, so someone who enables it will hear it on every deliberate close and think it is misfiring.
• pr-ci-failed is only seen while the roster is on screen. The phase poll doesn't run otherwise, so a failure that lands while the user is in another view is never noticed. It is not a background CI watcher; don't offer it as one.

Sound — global

Settings has a UI for this (Notification sounds), so use this skill when the user wants something the UI makes tedious — a different sound per moment, or per project.

{
  "soundKinds": ["finished", "waiting", "command-failed"],
  "sounds": { "waiting": "preset:coin", "command-failed": "preset:gong" },
  "soundFile": "/Users/you/sounds/done.mp3"
}

• soundKinds — which moments beep. Omit to keep ["finished", "waiting"]; [] for silence. Listing a kind here is what makes it audible at all — a sounds entry for a kind that isn't in soundKinds plays nothing.
• sounds — per-kind sound. A preset:<id> or an absolute path. A kind with no entry falls back to soundFile, and then to the built-in chime.
• soundFile — the fallback for every kind. Absolute path.