Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here
claude-code-notify-plugin logo

claude-code-notify-plugin

mocha-plugins

OtherClaude Codeby Xibo Wang

Summary

POST Claude Code Notification, PreToolUse:ExitPlanMode, PreToolUse:AskUserQuestion, and Stop hook events to a webhook URL.

Install to Claude Code

/plugin install claude-code-notify-plugin@mocha-plugins

Run in Claude Code. Add the marketplace first with /plugin marketplace add Mocha--/claude-code-notify-plugin if you haven't already.

README.md

claude-code-notify-plugin

Overview

Bash hooks that POST to a webhook URL whenever Claude needs you:

  • Notification — permission prompts and MCP elicitation dialogs (matcher: permission_prompt|elicitation_dialog).
  • PreToolUse:ExitPlanMode — when Claude exits plan mode and waits for plan approval.
  • PreToolUse:AskUserQuestion — when Claude opens an AskUserQuestion picker and waits for your selection.
  • Stop — when Claude finishes a turn.

Install

In Claude Code.

1. Add the marketplace

/plugin marketplace add Mocha--/claude-code-notify-plugin

2. Install the plugin

/plugin install claude-code-notify-plugin@mocha-plugins

Configure

Three environment variables are required:

| Variable | Required | Description | |---|---|---| | CLAUDE_NOTIFY_WEBHOOK_URL | yes | Webhook URL. | | CLAUDE_NOTIFY_NOTIFICATION_PAYLOAD | yes | JSON body for Notification, PreToolUse:ExitPlanMode, and PreToolUse:AskUserQuestion. POSTed verbatim. | | CLAUDE_NOTIFY_STOP_PAYLOAD | yes | JSON body for Stop. POSTed verbatim. |

If any of these variables is missing, the hook exits non-zero and prints an error to stderr. Disable the plugin with /plugin disable if you want to silence it temporarily.

Pick one of:

Option A — guided setup via skill

After installing the plugin, ask Claude:

configure notify plugin

This invokes the bundled configure skill, which inspects your existing config (shell rc files + ~/.claude/settings.json), asks where to write the vars, generates payloads for Slack / Discord / ntfy / custom shapes, and writes them for you.

Option B — set them manually

Export them in ~/.zshrc, ~/.bashrc, or add them under env in ~/.claude/settings.json. See Payload examples below.

After either option, restart Claude Code so the hook subprocess inherits the new env.

Payload examples

The payload shape is entirely up to you — whatever JSON your webhook accepts. The plugin POSTs the value as application/json exactly as set, with no templating or substitution. The examples below are just starting points for common destinations:

export CLAUDE_NOTIFY_WEBHOOK_URL="https://hooks.slack.com/triggers/..."

# Slack workflow trigger
export CLAUDE_NOTIFY_NOTIFICATION_PAYLOAD='{"origin":"🌰 Devbox","message":"🚨 Waiting for input"}'
export CLAUDE_NOTIFY_STOP_PAYLOAD='{"origin":"🌰 Devbox","message":"✅ Complete"}'

# Discord
export CLAUDE_NOTIFY_NOTIFICATION_PAYLOAD='{"content":"🚨 Claude needs you"}'
export CLAUDE_NOTIFY_STOP_PAYLOAD='{"content":"✅ Claude finished"}'

# ntfy
export CLAUDE_NOTIFY_NOTIFICATION_PAYLOAD='{"topic":"claude","title":"Claude","message":"Waiting for input"}'
export CLAUDE_NOTIFY_STOP_PAYLOAD='{"topic":"claude","title":"Claude","message":"Complete"}'

For anything else, check your webhook's docs for the expected request body and put that JSON in the payload variables.

Requirements

bash and curl. That's it.

Related plugins

Browse all →