How to get notified when Claude Code finishes (Mac and Windows)
Three ways to know the moment Claude Code is done or needs your permission: terminal notifications, a Stop hook, or a desktop buddy that shows it on screen.
Updated October 15, 2026
Claude Code is at its best on long tasks: refactors, test runs, migrations. That's also when you switch to Slack or email, and then forget to check back. Meanwhile Claude has either finished, or it's been sitting on a permission prompt for twenty minutes waiting for a “yes”.
Here are three ways to get told the moment it's done or needs you, from zero setup to fully hands-off.
1. Use a terminal that shows Claude Code's notifications
Claude Code can send a notification when it finishes or needs input, but whether you see it depends on your terminal. Terminals with native notification support, such as iTerm2, Ghostty and Kitty, can show it as a system notification. The integrated terminals in VS Code and many other apps usually don't.
Good for: one session in a dedicated terminal. Not great for: Claude Code inside an IDE, or several sessions at once.
2. Add a Stop hook that sends a notification
Claude Code hooks run a command when something happens. The Stop event fires when Claude finishes responding, and the Notification event fires when it needs your permission or input. Add them to ~/.claude/settings.json (merge with anything already there):
macOS
{
"hooks": {
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "osascript -e 'display notification \"Claude Code is done\" with title \"Claude Code\" sound name \"Glass\"'"
}
]
}
],
"Notification": [
{
"hooks": [
{
"type": "command",
"command": "osascript -e 'display notification \"Claude Code needs you\" with title \"Claude Code\" sound name \"Ping\"'"
}
]
}
]
}
}The first time it runs, macOS may ask you to allow notifications for Script Editor or your terminal. Allow it in System Settings › Notifications.
Windows
Windows has no one-line equivalent of osascript for notifications, so the simplest reliable option is a sound when Claude finishes:
{
"hooks": {
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "powershell.exe -NoProfile -Command \"[System.Media.SystemSounds]::Asterisk.Play()\""
}
]
}
]
}
}Hooks load when a session starts, so open a new Claude Code session after editing the file. Good for: a free, no-install alert. Not great for: knowing which session finished, or what it did, without going back to look.
3. Let a desktop buddy show it on screen
Flincko takes the hooks idea further. It installs Claude Code hooks for you in one click, then shows a small animated buddy at the edge of your screen that acts out what Claude is doing: thinking, reading files, typing, running tests. When Claude needs permission, an amber bubble shows the question and you can click Allow or Deny right there. When it's done, a green bubble shows the first line of the reply, and clicking it brings that window to the front.
- Works in the terminal, VS Code and JetBrains, plus Cursor's agent and claude.ai, ChatGPT and Gemini in the browser.
- Follows several sessions at once and always shows the most urgent one.
- Everything stays on your computer: the hooks talk to Flincko locally.
Which one should you pick?
- One session in iTerm2, Ghostty or Kitty: option 1 may be all you need.
- You want a free alert anywhere: option 2.
- You run several sessions, use an IDE, or want to approve commands without switching windows: option 3.