❓ Question
nowWhat would you like to name the test file in /tmp/?
LESS WATCHING. MORE BUILDING.
Let your agent work. Know when it's done.
Sounds, desktop notifications and webhooks for Claude Code and Codex CLI.
Open source · Runs locally · Codex CLI beta
What would you like to name the test file in /tmp/?
Plan: Create test file in /tmp/
Done. Installation now comes right after the hero.
✏️ 3 edited ⏱ 35sFollow the steps below to add desktop notifications to Claude Code.
Choose a target operating system to reveal your command. Mobile and unknown browsers need an explicit choice.
THE RIGHT SIGNAL. AT THE RIGHT TIME.
Get a desktop notification when your agent finishes or needs your attention. Spend less time watching a terminal.
Pick sounds, set the volume, and choose an audio device. Keep the signals you want and quiet the rest.
Send updates to Slack, Discord, Telegram, Teams and more. Configure webhooks for wherever you work.
Click-to-focus support depends on your terminal and OS. See platform details ↗
A FEW THINGS TO KNOW
Everything you need to get back to work.
No. Select Claude Code, Codex CLI, or both. Install the selected agent CLI first; the command installs this notification plugin.
Yes. The installer registers the hooks and saves a stable runtime copy. Open /hooks in Codex to review and trust them. Changed definitions need review again.
The installer preserves your shared configuration and foreign Codex hooks. Install and update use the same command. Restart the selected agent after updating.
Yes. Configure sounds, volume, audio device and notification channels. Choose Configure in the guide for the steps specific to your agent.
Support varies by OS and terminal. iTerm2 needs its Python API for precise tab targeting. Windows focuses a window, not an exact tab. Check supported environments.
Check your OS notification permissions and chosen channels. For Codex, confirm the hooks are trusted. Follow troubleshooting for platform-specific checks.
LET YOUR AGENT TAKE THE NEXT TURN