TapNoiseA done sound means the integration received a completion event. It does not independently verify the agent’s reasoning, your requirements, the test result or the safety of the resulting code.
Read the result before continuing
Return to the agent and inspect its final message. Did it complete the task, ask a question, encounter a limit or leave a manual step? A turn can finish without the overall job being finished.
Look at the diff and run the checks appropriate to the change. For a build failure, read the output rather than relying on whether an alert sounded cheerful.
Keep separate states meaningful
TapNoise provides Done, Needs you and Error cues where the connected agent supports those events. The available set differs by integration: Claude Code has all three, Cursor has done and error, and the current Codex integration reports done.
The absence of an error cue is not evidence of no errors. Some failures occur inside work that later produces a normal final response.
Use audio to change attention
The useful workflow is “hear the cue, inspect the result, decide the next action.” It lets you stop watching a terminal continuously while keeping the actual review with you.
For direct command execution, a success-versus-failure terminal sound can reflect an exit status, which is still narrower than correctness. For connection trouble, use agent sound diagnostics.
Sources: TapNoise event support, Cursor stop event.