Claude Code Notification Builder

Add a Stop hook. Claude Code fires the Stop event when it finishes responding, and any command you register runs with the event JSON on stdin. This builder generates the settings.json block and a notify script for your channel — desktop toast, Discord, Slack, Telegram, or ntfy.sh — so you get pinged the moment the task is done.

Yes. Both take an incoming-webhook URL: create one in Discord under Server Settings → Integrations → Webhooks, or in Slack under api.slack.com/apps → Incoming Webhooks. A Stop or Notification hook script then posts the message with a single curl call. This builder writes that script for you, with a jq-free fallback for machines without jq.

Yes. Create a bot with @BotFather to get a token, find your chat ID (message @userinfobot, or send your bot a message and read getUpdates), and a hook script can call the Bot API sendMessage endpoint with curl. The builder generates the script with your token and chat ID baked in — locally, in your browser.

Three ways. Hooks: point them at ntfy.sh or Telegram and the push lands on your phone — works everywhere, any terminal, any number of sessions. Native: Claude Code ships Remote Control push notifications (v2.1.110+), but they cover claude.ai-connected sessions and one agent at a time. Ambient: Backgrind Live mode streams every agent — Claude Code, Codex, Cursor CLI, OpenCode — to your phone with zero hook plumbing.

Stop fires when Claude Code finishes its whole response — the task-done signal. Notification fires mid-task when it needs you: a permission prompt or an idle wait for input. If you only want the permission asks, the Notification event accepts a matcher such as permission_prompt, and the builder can set that for you.

No. The builder is fully client-side — nothing is sent to any server, nothing is stored, and there is no signup. Your URLs and tokens are embedded into the generated scripts locally and only exist in the files you copy or download yourself.

~/.claude/settings.json applies to every project on your machine — the usual choice for notifications. .claude/settings.json lives inside one repo and gets committed, so the whole team shares the hooks. .claude/settings.local.json is per-repo but gitignored — project-specific and private to you. The builder adjusts paths and install steps for whichever scope you pick.

Not natively — the Stop event payload carries no duration field (verified against the official hooks reference). The builder works around it honestly: a UserPromptSubmit hook records a start timestamp per session, and the notify scripts compare it on Stop and stay silent under your threshold. If the timestamp file is missing, they notify anyway rather than fail silently.