TapNoiseMoving an app can leave an integration pointing at its previous location. TapNoise’s Agents page detects an outdated or moved connection and offers Repair.
Put the app where it will stay
Move TapNoise.app into Applications and launch that copy. Avoid connecting agents from the mounted disk image or a temporary download location, since that path may disappear when you eject or clean up.
Close duplicate copies so you know which version owns the settings window. Then inspect Settings › Agents for the specific integration that needs attention.
Use Repair rather than replacing files
Choose Repair where offered. TapNoise maintains a stable helper under its Application Support directory and updates the integration to use the intended app copy.
Its config-editing code backs up settings before making changes. Do not delete an agent’s full JSON or TOML configuration to fix a notification path; that can remove unrelated preferences and hooks.
Verify a new turn
Restart the relevant local agent session if needed and run a small test. Preview a Done cue first to confirm playback independently from configuration.
If a custom notification command already existed, check that it still behaves as expected. For removal rather than repair, remove the integration through TapNoise before deleting the app. For a wider diagnostic sequence, see missing agent sounds.
Sources: TapNoise repair behaviour, agent connection setup.