Agent Sounds

When to use

• •User wants local audio feedback for agent events.
• •User wants to create or validate a sound preset.
• •User wants to wire Claude/Codex/OpenCode events to agent-sounds.

Core workflow

1. •Verify runtime:
   • •agent-sounds ls
   • •agent-sounds events
2. •Create a preset if needed:
   • •place files in ~/.agent-sounds/presets/<preset>/sounds/
   • •write ~/.agent-sounds/presets/<preset>/preset.json
3. •Select preset:
   • •agent-sounds use <preset>
4. •Test playback:
   • •agent-sounds play notification
5. •Quick preset check:
   • •jq empty presets/<preset-name>/preset.json

Fetch strategy:

• •Prefer direct file URLs + bulk download (curl/wget).
• •Do not add fetchers to runtime; keep fetch scripts external/reference-only.

References

• •Preset schema + event contract: references/PRESET_FORMAT.md
• •Claude hooks example: references/claude-hooks.json
• •Codex notify example: references/codex-notify.toml
• •OpenCode plugin example: references/opencode-plugin.js
• •Optional fetch-script examples: gist

Rules

• •Keep runtime usage to playback primitives only.
• •Treat adapter files as reference-only; edit for local setup.
• •Merge config changes only; never replace unrelated user settings.