notify-permission — Claude Code plugin: what it does, how to install
notify-permission sends Slack cards when Claude Code waits for permissions or user input, freeing you from watching long-running terminal tasks.
MIT ★ 586 updated 2026-10-26
/plugin marketplace add karanb192/claude-code-hooks
/plugin install notify-permission@claude-code-hooksWhat notify-permission does
The plugin hooks into permission_prompt, idle_prompt, and elicitation_dialog notification events. Whenever Claude Code needs approval for Bash, file writes, edits, or reads, it constructs a Slack Block Kit message. Each card shows the project name, current working directory, a timestamp, a 6-character session prefix, and the prompt message capped at 200 characters.
Outbound alerts require the CCH_SLA_WEBHOOK environment variable. Without this variable, the hook logs a NONE entry and skips network calls entirely. It always exits with code 0 and outputs {}, ensuring broken webhooks or invalid payloads never freeze the terminal session. All inputs and webhook results are stored in ~/.claude/hooks-logs/<date>.jsonl.
What it helps with
- send Slack alerts on tool permission prompts like Bash or file edits
- track when Claude Code idles or asks for clarifying input
- review session context and working directories directly in Slack cards
- record notification events into local JSONL files for inspection
Example prompts for the agent
- Run the test suite and apply any needed database migrations
- Execute the build script in Bash and update config files
- Refactor the authentication service and run full integration checks
How to install notify-permission
Plugin marketplace
/plugin marketplace add karanb192/claude-code-hooks/plugin install notify-permission@claude-code-hooksStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about notify-permission
How to install notify-permission in Claude Code?
Run /plugin marketplace add karanb192/claude-code-hooks, then run /plugin install notify-permission@claude-code-hooks and restart Claude Code.
What does notify-permission do?
It intercepts user confirmation and idle prompts in Claude Code and delivers formatted Block Kit cards directly to a Slack webhook.
What happens if CCH_SLA_WEBHOOK is not configured?
The hook skips all network requests and writes a NONE entry to disk. Claude Code continues normally because the script always exits with code 0.
Source text
notify-permission · MIT
# notify-permission
> Sends Slack alerts when Claude needs your input, so you stop babysitting the terminal.
A `Notification` hook fires on `permission_prompt`, `idle_prompt`, and `elicitation_dialog`, classifies the notification (from `notification_type` when the payload carries it, otherwise from keywords in the message), and posts a Slack Block Kit card to your webhook: an emoji plus a specific title (which tool needs permission: Bash, Write, Edit, or Read; Claude waiting; or a choice to make), the project name, a short session id, the message truncated to 200 chars, the full cwd, and a timestamp. Kick off a long task, walk away, and Slack pings you the moment Claude is blocked on you.
## Install
```
/plugin marketplace add karanb192/claude-code-hooks # once per machine
/plugin install notify-permission@claude-code-hooks
```
Restart Claude Code, done. (Or from a shell: `claude plugin install notify-permission@claude-code-hooks`.)
## What it does
| Event | Runs | What happens |
|-------|------|--------------|
| Notification (`permission_prompt\|idle_prompt\|elicitation_dialog`) | sync | Classifies the notification, posts a Slack card to `CCH_SLA_WEBHOOK`, logs the outcome. |
Every input, send, and failure is appended to `~/.claude/hooks-logs/<date>.jsonl`. The hook always exits 0 and prints `{}`; it never blocks your session, even on malformed input or a dead webhook.
## Configuration
One environment variable:
| Variable | Default | Purpose |
|----------|---------|---------|
| `CCH_SLA_WEBHOOK` | unset | Slack Incoming Webhook URL the alert card is posted to. Unset means the hook sends nothing and logs a `NONE` entry (nothing sent, no error). |
No safety levels, no ask mode; this is a notifier, not a guard. Discord and Telegram channels are planned but not wired up yet: today the hook sends to Slack only.
## Data & privacy
The only network call is the POST to the webhook you configure, and only when `CCH_SLA_WEBHOOK` is set. The card carries the notification message (truncated to 200 chars), the project directory path, and a 6-char session id prefix; everything else stays in the local log.
## Uninstall
```
/plugin uninstall notify-permission@claude-code-hooks
```
---
Part of [claude-code-hooks](https://github.com/karanb192/claude-code-hooks).
© Karan Bansal · MIT · karanb192/claude-code-hooks