TapNoiseCoding agents and Terminal guides for Mac
Useful completion cues for Claude Code, Codex, Cursor and commands running on your Mac.
- Agent sounds not working on Mac? Check these layersSeparate audio playback, quiet mode, connection state and agent event delivery before editing hook files or reconnecting every coding tool.
- An agent done sound does not mean the code is correctInterpret coding-agent completion cues as a signal to review, then check the diff, tests and remaining work before treating a turn as successful.
- Different Terminal sounds for success and failure on MacSave a command's exit status, play a distinct local cue for each outcome and return the original status so the notification cannot disguise a failed build.
- How to choose agent alert sounds you can recogniseGive completion, permission requests and failures distinct meanings, preview them at a modest level and avoid alerting on every small agent action.
- How to hear when a Cursor agent finishes on your MacConnect Cursor to TapNoise for a completion cue, test a small local turn and distinguish a finished agent loop from code that has passed review.
- How to hear when Claude Code needs permission on MacUse TapNoise's needs-you cue for Claude Code permission prompts, keep it distinct from completion and review the requested action before approving it.
- How to keep coding-agent alerts quiet during a meetingCheck TapNoise's microphone-based quiet mode, keep a visible way to return to the agent and test the actual headset and recording setup before a call.
- How to notice a long Mac build finishing without watching itChoose a local completion cue for a known build command, keep the build result visible and avoid treating a sound as proof that every check passed.
- How to play a sound when a Terminal command finishes on MacUse macOS afplay after a known command, choose whether failure should also alert you and keep notification errors separate from the command's result.
- How to remove agent sound hooks without losing other settingsDisconnect TapNoise from each agent before uninstalling, preserve unrelated configuration and understand why deleting an entire hooks file is unnecessary.
- How to return to a waiting coding agent by clicking TappyUse TapNoise's desktop companion as a way back to a waiting local agent, and understand how clicking differs from sensor-based MacBook knocks.
- How to show a Mac notification after a Terminal taskUse the built-in osascript command for a simple completion notification, keep private command output out of the message and check notification permissions.
- Local vs remote coding-agent alerts: where does the sound play?A hook runs in the agent's environment. Understand why SSH, containers and cloud jobs do not automatically send a local Mac sound to your speakers.
- What a local coding-agent sound hook can seeHooks can receive rich event data even when a sound helper only uses status. Review the command, payload handling and network behaviour before connecting one.
- Why agent alerts can need repair after moving TapNoiseKeep TapNoise in Applications, inspect its Agents connection state and use Repair to update the helper path while preserving other agent settings.
- How to get a sound when Claude Code finishesHear when Claude Code is done or needs you. Use its built-in hooks with a macOS sound, or let TapNoise connect it for you in Settings > Agents.
- How to know when Codex is done on your MacCodex can run a command when a turn ends. Set that up yourself, or let TapNoise connect Codex in Settings > Agents and play a sound when it finishes.