Play a Sound When Claude Finishes with a Stop Hook
If you're stepping away while Claude works, you need a way to know when it's done. Polling the terminal every few minutes defeats the purpose of automation.
Add a Stop hook that plays a sound the moment Claude finishes its turn. On macOS, afplay can play any system sound without installing anything.
Add this to your ~/.claude/settings.json:
{
"hooks": {
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "afplay /System/Library/Sounds/Blow.aiff"
}
]
}
]
}
}
The Stop hook fires every time Claude finishes a turn and returns control to you. Walk away, make a coffee, switch to a different task — when you hear the sound, Claude is waiting.
You can swap in any sound from /System/Library/Sounds/:
# Preview available sounds
ls /System/Library/Sounds/
# Basso.aiff, Blow.aiff, Bottle.aiff, Frog.aiff, Glass.aiff...
afplay /System/Library/Sounds/Glass.aiff
This becomes especially useful when running multiple parallel sessions. Different sessions can play different sounds so you know which window just finished.
A two-line hook turns Claude into something that actually tells you when it's done.
via @mvanhorn
Log in to leave a comment.
When Claude writes error messages, button labels, validation text, or onboarding flows, it defaults to generic developer-speak. Add a "Users" section to your CLAUDE.md describing who your actual users are — their technical level, industry jargon, and what they care about — so Claude writes copy that makes sense to THEM, not to developers.
Use the --agent flag with custom markdown files in .claude/agents/ to launch purpose-built Claude sessions with restricted tools and scoped system prompts.
Every project has traps — the billing module that silently fails if you forget to queue the job, the legacy table with column names that don't match the model, the config value that must be set before tests run. Document these gotchas in your CLAUDE.md so Claude avoids the same mistakes your team spent days debugging.