TapNoiseA notification command runs where the agent runs. If that is a remote server, container or cloud environment, a local Mac sound command is not automatically available or audible on your laptop.
Draw the execution path
Identify where the agent process reads its configuration, where the hook command exists and where audio would be played. A path under your Mac’s home directory may not exist in a container or on an SSH host.
The terminal window you see is only the interface. It does not make every process displayed inside it a local macOS process.
TapNoise’s supported path
TapNoise connects agents installed on the Mac and uses a local helper and listener. Its desktop interactions also depend on a local app window that it can bring forward.
Installing TapNoise on your Mac therefore does not configure a remote Claude Code instance or a hosted job. Treat those as separate environments and use their intended completion channels.
Avoid an unsafe shortcut
Do not expose a local listener publicly or forward entire agent payloads to a random service simply to get a chime. Any remote notification design should minimise transmitted data and use deliberate authentication.
For a normal local setup, use the connection guide. For an agent already connected but silent, debug the layers before assuming it needs network access.
Sources: TapNoise local requirements, Claude Code hook execution model.