TapNoiseClaude Code can need your permission before continuing. TapNoise gives that event a different cue from an ordinary finished turn, so you can tell that work is waiting for a decision.
Connect the local integration
Open TapNoise Settings › Agents and connect Claude Code. The app adds a Notification hook for the permission-prompt event, alongside its completion and error connections, after backing up the existing settings.
Use a fresh Claude Code session for the test. Preview Needs you in TapNoise first so you know which sound you are trying to recognise.
Return to the decision
Click Tappy to bring a waiting agent’s app forward. Compatible MacBooks can also use the agent double-knock action when enabled. Inspect the actual requested action before granting permission.
The cue is a request for attention, not a recommendation to approve. A command that deletes files or sends data still deserves the same review it would need without an audible reminder.
Avoid treating every notification alike
An idle reminder, a completed response and a permission prompt are different events. A broadly matched manual hook can produce more alerts than you intended; consult the current Claude Code hook documentation before editing matchers yourself.
For completion instead, use the Claude Code done guide. For the events TapNoise currently supports across agents, see cue meanings.
Sources: Claude Code Notification hooks, TapNoise’s cue meanings.