Add app notification ICONS and sound Settings

[llity]

Evaluate whether it is necessary to add two functions

[ShunmeiCho]

Thanks for the suggestion, @llity — both are useful, so I've implemented them as local, opt-in settings. They're read by the macOS daemon's environment only (never from the remote payload), and will land in an upcoming release.

Sound

Configurable per urgency tier. Defaults preserve today's behavior — only tool-approval prompts make a sound:

Variable	Applies to	Default
CC_CLIP_SOUND_CRITICAL	Tool approval needed	Glass
CC_CLIP_SOUND_ATTENTION	Idle / interrupted / Codex / opencode / Antigravity	silent
CC_CLIP_SOUND_CALM	"Claude finished" (end of turn)	silent

Values are macOS system sound names (Ping, Pop, Sosumi, …); none/off/silent mutes a tier. A per-notification sound field still overrides these.

App icon

CC_CLIP_NOTIFY_APP_ICON points at a local .png/.icns. Two honest limitations:

• Only works on the terminal-notifier path. The osascript fallback can't set a custom app icon (macOS derives it from the calling process), so without terminal-notifier the icon is unchanged.
• If you use cmux/tmux delivery, that path is tried first and only carries title/body, so sound + icon are skipped there.

Two questions before I finalize

1. Is per-urgency-tier sound enough, or do you want per-event sounds (e.g. distinct sounds for Codex-done vs Claude-stop)?
2. For the icon: point at your own file (current design), or would a bundled default cc-clip icon be more useful?

[llity]

Yes. My preferred design is profile-based notification settings.

Different CLI tools should be able to use different sounds and icons. For example, Codex CLI, Claude CLI and Gemini CLI may each have their own notification sound, so users can identify which tool needs attention without checking the terminal.

It would also be useful if icon_key could be customized and mapped to custom SVG icons.

[ShunmeiCho]

Thanks @llity — that makes sense. Profile-based, per-tool notification settings (each CLI with its own sound + icon, so you can tell which tool needs attention) plus a customizable icon_key mapped to custom SVG icons is a good direction.

A first step just landed in #95: opt-in, env-configurable sound (per urgency tier) and a custom app icon (CC_CLIP_NOTIFY_APP_ICON), read locally. It is global rather than per-tool, so it does not yet cover the profile-based design you described.

Keeping this issue open to track the per-tool profile model + icon_key/SVG mapping as the follow-up. Thanks for the clear spec!